Resolution and Scope Tools

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.

​

Sequencing habits

• Resolve only when the host truly lacks the right scope.
• Keep schedule-style flows bounded before branching into deeper tools.

​

Decision guide

​

Tool-by-tool guidance

​

resolve_entities

• Job: Resolve fuzzy sports language into bounded candidates with provider refs, crosswalk confidence, and disambiguation options.
• Source ownership: GSD Lookup primary
• Use it when: the host does not yet know which sport, competition, competition season, series, participant, or venue the user means.
• Do not use it when: the caller already has a stable provider ref and only needs schedule, standings, watchability, or event detail.

​

list_schedule

• Job: Return the competitive deep-sports schedule for a bounded sport, competition, competition season, series, series season, or participant scope.
• Source ownership: GSD Lookup primary
• Use it when: the question is about the sports calendar itself and GSD should remain the source of truth.
• Do not use it when: the product is explicitly asking what is watchable; use list_watchable_schedule or list_live_slate instead.

​

list_watchable_schedule

• Job: Return bounded schedule rows enriched with grounded watchability semantics when available, otherwise return truthful evidence-backed fallback rows with explicit limitations.
• Source ownership: Dedicated availability primary when provisioned, otherwise bounded sports-truth rows plus explicit fallback watchability evidence
• Use it when: the user is really asking what can be watched in a bounded window.
• Do not use it when: the answer must stay purely competition-first or when the host needs standings, actions, or stats.

​

list_live_slate

• Job: Return what is live or imminently live from GSD sports truth, with optional watchability overlay when the availability contract is provisioned.
• Source ownership: GSD Lookup primary, dedicated availability overlay optional
• Use it when: Use it for what-is-on-now, live slates, and watchability-first entry points.
• Do not use it when: Do not use it to answer standings, historic season questions, or non-bounded schedule browse flows.

​

get_competition_structure

• Job: Return normalized competition structure and hierarchy for a league or competition season.
• Source ownership: GSD Lookup primary
• Use it when: the host needs the tournament tree, phase layout, or season hierarchy before calling deeper tools.
• Do not use it when: Do not use it if the product only needs current standings, one event, or watchability.

​

Next steps

• Use Tool Catalog when you want the full 1.4.1 surface in one place.
• Use ID Acquisition and Tool Sequencing when the host still needs provider refs or a safer tool order.
• Use Prompt-to-Tool Mapping when you want a proven low-token workflow for a real user prompt.