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.

​
ID Acquisition and Tool Sequencing

Use this page when you know the product job but do not yet know which provider refs or bounded scopes you need to collect first.

​
Common refs and what they unlock

Ref or scopeUsually get it fromThen use
competitionIdresolve_entitieslist_schedule, get_competition_hub, list_watchable_schedule
competitionSeasonIdresolve_entities or get_competition_structureget_standings, get_rankings, get_competition_hub
eventIdlist_schedule, list_watchable_schedule, or list_live_slateget_event_summary, get_event_center, get_watch_availability
participantIdresolve_entitiesget_participant_profile, get_roster, list_schedule
venueIdresolve_entities or list_watchable_scheduleget_venue_profile, get_program_context
programIdyour program guide or list_programs_for_entitylist_entities_for_program, get_program_context, get_watch_availability

​
Choose a sequencing pattern

  1. Call resolve_entities only if the user prompt is genuinely ambiguous. 2. Keep the returned provider refs in their original namespace. 3. Move into the smallest next tool that matches the job.

​
Safe sequencing rules

  1. Reuse provider refs instead of re-resolving the same object.
  2. Keep timeFrom and timeTo bounded for schedule, live, and watchability flows.
  3. Use GSD-first tools for sports truth and watchability-first tools for watchability.
  4. Respect meta.crosswalkConfidence before enriching across providers.
  5. Treat meta.agentHints.recommendedNextTools as hints, not as mandatory fanout.

​
Common low-token workflows

​
Competition to event to event center

  1. Call list_schedule with a bounded window.
  2. Select the correct eventId.
  3. Move into get_event_center only if the product needs more than a summary.

​
Competition to watchable schedule to watch availability

  1. Call list_watchable_schedule with a bounded window.
  2. Select the correct watchable row.
  3. Move into get_watch_availability for the normalized answer.

​
Program to context to watchability

  1. Start from get_program_context.
  2. Use the returned sports context to choose the next candidate-set call in the host.
  3. Move into get_watch_availability only when the UX needs a direct where-to-watch answer.

​
Read this next