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_stats
Family: Deep Sports Truth Tools
Return raw event stats plus normalized team and person stat groups with canonical metric keys.
the answer needs performance numbers rather than a summary or timeline.
Source ownership: GSD Lookup
Use something smaller or different when
the question is just about availability or schedule position.
Plain-English prerequisites
This tool does not require a prerequisite ID beyond the scoped inputs shown below.
Input What 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.
Input What 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.
Sequencing guidance
Needed ID or scope Call this first Then use scope Tool Catalog Start from the smallest tool that can safely anchor the workflow, then deepen only if the user asks for more.
Response highlights
Raw teamStats and personStats payloads from the provider.
Normalized teamGroups and personGroups with participant identity and canonical metrics maps.
Curated availableMetrics and metricAvailability, including expected-goals availability when present.
Response shape
Field What it means data.teamStats / data.personStatsRaw provider event-stat payloads for teams and people. data.teamGroups[] / data.personGroups[]Normalized stat groups suitable for direct host rendering. data.availableMetrics[]Union of metric keys actually confirmed in this response. data.metricAvailabilityFlags for important derived metrics such as expected goals.
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
JSON-RPC
curl
TypeScript
Python
{
"jsonrpc" : "2.0" ,
"id" : "tool-call-1" ,
"method" : "tools/call" ,
"params" : {
"name" : "get_event_stats" ,
"arguments" : {
"eventId" : "MATCH_ID"
}
}
}
Use get_event_stats when the host already knows the right scope and needs this job directly.
Common mistakes
Calling get_event_stats before the host has the right provider refs or bounded window.
Using get_event_stats when a smaller sibling tool would answer the question more directly.