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.
Dual-Source Doctrine
Sports MCP Server is not a thin wrapper around provider endpoint parity. It is a product-shaped contract that picks a source family based on the job the user is actually asking you to solve.Start with the job, not the upstream
- Competition-first sports truth
- Availability-first watchability
- Bounded hybrid composition
Use GSD-first flows when the product question is about the sport itself.Good fits:
- standings, rankings, tables, ladders, and playoff picture
- competition structure, phases, and season context
- event summary, timeline, lineups, stats, and odds
- roster and participant identity pages
The important boundary
Schedule is a dual-source domain, but the two schedule tools mean different things:| Tool | Source ownership | Use it for |
|---|---|---|
list_schedule | GSD-led | Competitive schedule truth, season browse, event selection, and deep sports workflows |
list_watchable_schedule | Supported availability contract when provisioned, otherwise GSD-led stateless watchability evidence | Watchable rows, curated schedule semantics, and program-aware browse experiences |
list_live_slate | GSD-led with optional availability overlay | What is live or imminently live right now |
Design rules
- GSD must not fake watchability.
- Watchability adapters must not fake standings, actions, stats, or odds.
- Hybrid enrichment should stay explicit, bounded, and explainable.
- If cross-provider linkage is weak, return ambiguity or partials instead of guessing.