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.
Sports MCP Server
This documentation covers the Gracenote Sports MCP Server, its public tool surface, its source-ownership model, and the recommended integration paths for MCP hosts and clients.What This Docs Set Covers
Server responsibilities
- Read-only sports retrieval through MCP
- Public tool definitions and argument validation
- Bounded cross-source retrieval
- Deterministic envelopes with explicit
partial,limitations,missingSections, andsources
Source ownership
GSD Lookupfor deep sports truth- Dedicated availability contract for grounded where-to-watch flows
On Programsfor program-first sports contextSportsEventCurrentonly for freshness on already linked watch/program rowsGSD Metadatafor bounded enrichment
Common product jobs
- Resolve sports entities and IDs
- Browse league, team, and tour schedules
- Read standings, rankings, and event detail
- Ask where to watch a known game, event, or competition
- Build bounded competition hubs, series hubs, and event-center views
Start Here
| If you need | Go here |
|---|---|
| First successful calls | Quickstart |
| Transport and auth basics | Connect and Call Tools |
| Tool selection by job | Tool Catalog |
| IDs, crosswalks, and bounded windows | IDs, Crosswalks, and Bounded Windows |
| Watchability and program connectivity | Program Connectivity and Watchability Tools |
| Competition, series, and event bundles | Hybrid Bundle Tools |
Documentation Map
Getting started
Core concepts
Tool families
- Resolution and Scope Tools
- Deep Sports Truth Tools
- Program Connectivity and Watchability Tools
- Hybrid Bundle Tools
- Media and Assets Tools
- Tool Catalog
Prompt-to-tool mapping
- Prompt Library
- What Is On Today?
- Where Can I Watch This Game?
- What Does the League or Tournament Picture Look Like?
Current Surface
Sports MCP Server1.4.1 exposes a 24-tool public catalog. The server remains stateless and read-only, and it does not turn itself into the host, client, or assistant layer.
The host or client still owns:
- deciding which tool to call
- orchestration across multiple tool calls
- comparison logic
- permissions and review flow
- end-user wording and presentation