Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.etonecarg.com/llms.txt

Use this file to discover all available pages before exploring further.

Canonical tool name: list_schedule Family: Resolution and Scope Tools

​
What this tool is best at

Return the competitive deep-sports schedule for a bounded sport, competition, competition season, series, series season, or participant scope.

​
Choose this tool when

  • the question is about the sports calendar itself and GSD should remain the source of truth.
  • Source ownership: GSD Lookup primary

​
Use something smaller or different when

  • the product is explicitly asking what is watchable; use list_watchable_schedule or list_live_slate instead.

​
Inputs you need

​
Plain-English prerequisites

  • sportId / seriesId / seriesSeasonId / competitionId / competitionSeasonId / participantId: Provide one bounded schedule anchor plus timeFrom and timeTo.

​
Required inputs in the public contract

InputWhat it means
timeFromBounded window start. Use an ISO date or timestamp that matches the user’s browse moment or watchability horizon. Some tools require this field as part of the public contract.
timeToBounded window end. Keep it tight enough that the request still represents one real product moment. Some tools require this field as part of the public contract.

​
Optional inputs in the public contract

InputWhat it means
sportIdGSD-facing sport ref for a sport-wide schedule query.
competitionIdGSD-facing competition ref for a competition-first schedule query.
competitionSeasonIdGSD-facing season ref when the host wants one competition season instead of the broader competition.
seriesIdGSD-facing series ref for a tour-wide or motorsport schedule query.
seriesSeasonIdGSD-facing series-season ref when the host wants one tour season window.
participantIdGSD-facing participant ref when the schedule should be anchored to one team or participant.
limitMaximum number of rows to return. Keep it small for low-token UX and larger only when the UI truly needs a browse list.
languageOptional BCP 47 language hint such as en-US. Use it when the host needs translated provider output.

​
Sequencing guidance

Needed ID or scopeCall this firstThen use
scopeTool CatalogStart from the smallest tool that can safely anchor the workflow, then deepen only if the user asks for more.
  • Use this tool to identify the right event row before opening deeper event tools.
  • Stay in GSD-first tools after this call unless the UX explicitly shifts into watchability.

​
Response highlights

  • Top-level schedule rows are returned in data.items[]; there is no separate data.schedule[] object in the public contract.
  • Each row carries the reusable event refs, compact participant summary, status, and any exposed phaseRefs or overallRefs.
  • The response also returns data.scope and data.seasonFilterApplied so the host can see the final bounded browse scope.

​
Response shape

FieldWhat it means
data.items[]Bounded schedule rows for the selected scope and time window.
data.items[].eventIdReusable event ref for later event-detail calls.
data.items[].sportsEventGIdSecondary event-evidence ref when the selected row exposes it.
data.items[].name / startTime / statusCompact event identity and timing fields for list rendering.
data.items[].participants[]Compact participant-side summary for each schedule row.
data.items[].phaseRefs[] / overallRefs[]Actionable deeper refs when the upstream row exposes them.
data.scopeEcho of the final browse scope and bounded window used by the server.
data.seasonFilterAppliedWhether the server narrowed the result to a season-specific slice.

​
Reuse next

  • Reuse provider refs returned by this tool to avoid resolving the same entity again.
  • Read meta.agentHints.recommendedNextTools and meta.agentHints.disambiguationOptions as non-binding host hints.

​
Example requests

{
  "jsonrpc": "2.0",
  "id": "tool-call-1",
  "method": "tools/call",
  "params": {
    "name": "list_schedule",
    "arguments": {
      "competitionId": "LEAGUE_ID",
      "timeFrom": "2026-04-08",
      "timeTo": "2026-04-09"
    }
  }
}

​
Previous-step tools

​
Next-step tools

​
Alternative tools

​
Prompt patterns this tool fits

  • Use list_schedule when the host already knows the right scope and needs this job directly.

​
Common mistakes

  • Using an open-ended window. All schedule flows are intentionally bounded.
  • Assuming GSD schedule rows imply watchability. They do not.