Deep Sports Truth 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.

Use GSD-first tools for standings, structure, stats, actions, lineups, odds, rosters, and profiles. Use this family when the workflow fits this source-ownership boundary. Move to the tool page once you know the exact job and scope.

​

Sequencing habits

• Prefer atomic tools before reaching for a bundle.
• Stay in GSD-first flows when the question is about standings, stats, lineups, odds, or structure.

​

Decision guide

​

Tool-by-tool guidance

​

get_event_summary

• Job: Return the minimum single-event sports-truth object needed to answer what the event is and what is happening in it at summary depth.
• Source ownership: GSD Lookup primary, On sports-event lookup optional when the caller already has On refs
• Use it when: Use it as the default entry point for one known event before fetching deeper sections.
• Do not use it when: the host needs play-by-play, lineups, stats, odds, or watchability detail in one response.

​

get_event_lineups

• Job: Return lineups and officials for one event.
• Source ownership: GSD Lookup
• Use it when: the answer needs the people on the field, court, grid, or match sheet.
• Do not use it when: Do not use it as a general event summary or a substitute for stats or actions.

​

get_event_timeline

• Job: Return the action stream or timeline for one event.
• Source ownership: GSD Lookup
• Use it when: the product needs scoring actions, incidents, laps, plays, or turning points.
• Do not use it when: Do not use it for lineups, aggregate stats, or watchability.

​

get_event_stats

• Job: Return raw event stats plus normalized team and person stat groups with canonical metric keys.
• Source ownership: GSD Lookup
• Use it when: the answer needs performance numbers rather than a summary or timeline.
• Do not use it when: the question is just about availability or schedule position.

​

get_phase_results

• Job: Return ordered phase or session results for qualifying, rounds, heats, groups, and similar staged competition slices.
• Source ownership: GSD Lookup
• Use it when: the host already knows the right phaseId and needs the ordered result rows for that stage or session.
• Do not use it when: Do not use it as a replacement for the full schedule, standings, or one-event summary.

​

get_odds

• Job: Return event odds when available.
• Source ownership: GSD Lookup
• Use it when: the product explicitly needs odds or betting-style implied probability context.
• Do not use it when: Do not use it for non-odds sports workflows or as a fallback when odds are missing.

​

get_standings

• Job: Return raw standings plus normalized table rows and group metadata for a competition or competition season.
• Source ownership: GSD Lookup
• Use it when: Use it for table, ladder, playoff-picture, and current-rank questions.
• Do not use it when: Do not use it for watchability, event detail, or generic ranking flows that are classification-based instead of table-based.

​

get_rankings

• Job: Return the richest non-empty leaderboard rows for a competition or series scope, plus selection metadata.
• Source ownership: GSD Lookup
• Use it when: the host needs leaderboards, driver standings, golf leaderboards, or category rankings rather than a single standings table.
• Do not use it when: Do not use it to replace standings, one-event stats, or phase/session results.

​

get_participant_profile

• Job: Return team, person, or university profile data with normalized refs and optional season context.
• Source ownership: GSD Lookup primary, On Universities enrichment optional
• Use it when: Use it for team hubs, player hubs, and participant identity pages.
• Do not use it when: the host only needs a roster list or one event’s lineups/stat line.

​

get_venue_profile

• Job: Return venue identity, geography, timezone, and normalized refs.
• Source ownership: On Sports Venues primary, GSD enrichment optional
• Use it when: the product needs venue context, travel/location framing, or venue-linked watchability browse flows.
• Do not use it when: the answer is really about a competition, team, or event instead.

​

get_roster

• Job: Return roster data for a team inside one competition context.
• Source ownership: GSD Lookup
• Use it when: the host needs the season-context roster and not just a single-event lineup.
• Do not use it when: Do not use it for people stats, lineups, or general team identity questions.

​

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.