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: get_event_summary Family: Deep Sports Truth Tools

​
What this tool is best at

Return the minimum single-event sports-truth object needed to answer what the event is and what is happening in it at summary depth.

​
Choose this tool when

  • Use it as the default entry point for one known event before fetching deeper sections.
  • Source ownership: GSD Lookup primary, On sports-event lookup optional when the caller already has On refs

​
Use something smaller or different when

  • the host needs play-by-play, lineups, stats, odds, or watchability detail in one response.

​
Inputs you need

​
Plain-English prerequisites

  • eventId: Use a GSD event ref when possible.

​
Required inputs in the public contract

InputWhat it means
eventIdProvider ref for one event. Prefer the GSD-facing event ref for deep-sports tools and the selected event row for hybrid follow-ons.

​
Optional inputs in the public contract

InputWhat it means
idSourceLookup-path hint for the supplied ID. auto uses namespace-aware routing, gsd treats the ID as sports-truth-facing, and on treats it as On-facing. It does not change source-of-truth ownership.
languageOptional BCP 47 language hint such as en-US. Use it when the host needs translated provider output.

​
Notes on optional inputs

  • idSource=auto uses namespace-aware routing. idSource=gsd treats the supplied ID as sports-truth-facing. idSource=on treats the supplied ID as an On sports-event ref.
  • idSource changes how the server looks up the event, not who owns the returned event truth.

​
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.

​
Response highlights

  • The summary includes event identity, competition or series context, timing, status, participant sides, score or result snapshot when available, venue, and reusable refs.
  • It explicitly excludes full lineups, play-by-play, stat groups, odds tables, watchability, media, and editorial.

​
Response shape

FieldWhat it means
data.summaryOne event summary object suitable for the default event-detail step.
data.summary.eventId / sportsEventGIdReusable primary and secondary event refs.
data.summary.name / startTime / statusCompact event identity and timing summary.
data.summary.participants[]Participant-side summary for the event.
data.summary.competition / series / venueContext objects the host can reuse for breadcrumbs and drill-downs.
data.summary.scoreBest available result snapshot for the event.
data.summary.phaseRefs[] / overallRefs[]Actionable refs that may be reused by later tools.

​
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": "get_event_summary",
    "arguments": {
      "eventId": "MATCH_ID"
    }
  }
}

​
Previous-step tools

​
Next-step tools

​
Alternative tools

  • No common alternatives.

​
Prompt patterns this tool fits

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

​
Common mistakes

  • Calling get_event_summary before the host has the right provider refs or bounded window.
  • Using get_event_summary when a smaller sibling tool would answer the question more directly.