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.

​
Connect and Call Tools

Sports MCP Server uses standard MCP JSON-RPC over HTTP. The safest first-call pattern is still:
  1. resolve scope when the prompt is ambiguous
  2. choose the right source family for the job
  3. deepen only if the user still needs more context

​
Connection model

This is the intended deployment model.Good fits:
  • application backends
  • orchestration workers
  • trusted MCP hosts
  • internal services that preserve product-scoped auth and telemetry

​
First request pattern

{
  "jsonrpc": "2.0",
  "id": "req-1",
  "method": "tools/call",
  "params": {
    "name": "resolve_entities",
    "arguments": {
      "query": "Premier League",
      "entityType": "competition",
      "limit": 5
    }
  }
}

​
Follow-on call patterns

Use this when the product needs sports truth first.Typical sequence:
  1. resolve_entities
  2. list_schedule or get_competition_hub
  3. get_event_summary or another atomic deep-sports tool

​
Working rules

  • Keep timeFrom and timeTo bounded anywhere the workflow is schedule-like or watchability-like.
  • Preserve the provider namespace of every ref you keep.
  • Use GSD-first tools for deep sports truth.
  • Use watchability and program-context tools for watchability jobs; they will use the supported availability contract when provisioned and otherwise degrade through the stateless fallback.
  • Read partial, missingSections, and limitations before deepening.

​
Read this next