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.
Response Envelopes and Partials
Sports MCP Server is explicit by design. A response can succeed and still tell you that one section was missing, ambiguous, or unsafe to enrich.Read the envelope before you deepen
| Field | Why it matters |
|---|---|
meta.partial | Tells you the answer is usable but incomplete |
meta.missingSections | Lists which parts of a bundle answer were intentionally not filled |
meta.sources | Preserves provenance across sports truth, program connectivity, current-state checks, and fallback evidence |
meta.crosswalkConfidence | Tells you whether cross-provider enrichment is safe for the selected result |
meta.agentHints.recommendedNextTools | Gives the host ordered, non-binding next-step hints |
meta.agentHints.disambiguationOptions | Helps you ask a narrowing question without guessing |
meta.limitations | Explains known gaps, ambiguity, or upstream constraints |
How to respond in the host
- Complete enough result
- Partial result
- Ambiguous result
A successful response with
partial: false is usually safe to render directly.Good host behavior:- render the answer
- preserve
meta.sourcesfor observability or QA - keep
meta.agentHints.recommendedNextToolsavailable only if the user drills down
Treat crosswalk confidence as a numeric workflow signal
| Band | Meaning | Safe host behavior |
|---|---|---|
0.90-1.00 | High confidence | Cross-provider enrichment may proceed when the product job requires it |
0.60-0.89 | Mixed confidence | Do not silently deepen across providers; narrow scope or stay inside one source family |
0.01-0.59 | Low confidence | Do not automatically cross providers |
null | No safe crosswalk | Do not assume linkage at all |
Example response shapes
- Partial bundle
- Ambiguous resolution
Partial bundle