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.

Quickstart

The fastest path to a successful integration is:
  1. resolve scope only when the prompt is ambiguous
  2. choose whether the job is competition-first or availability-first
  3. deepen only when the user actually needs more detail

Pick the right first path

Start with resolve_entities when the prompt is fuzzy and your host does not yet know which competition, participant, venue, or program the user means.
{
  "jsonrpc": "2.0",
  "id": "resolve-1",
  "method": "tools/call",
  "params": {
    "name": "resolve_entities",
    "arguments": {
      "query": "Premier League",
      "entityType": "competition",
      "resolutionProfile": "balanced",
      "limit": 5
    }
  }
}

Then choose the right schedule path

Use this when the user is asking about fixtures, rounds, matchups, or the sports calendar itself.
{
  "jsonrpc": "2.0",
  "id": "schedule-1",
  "method": "tools/call",
  "params": {
    "name": "list_schedule",
    "arguments": {
      "competitionId": "LEAGUE_ID",
      "timeFrom": "2026-04-08T00:00:00Z",
      "timeTo": "2026-04-09T00:00:00Z"
    }
  }
}

Open a single event only when needed

Use get_event_center when the product truly benefits from one coherent bundle.
{
  "jsonrpc": "2.0",
  "id": "event-1",
  "method": "tools/call",
  "params": {
    "name": "get_event_center",
    "arguments": {
      "eventId": "MATCH_ID",
      "timeFrom": "2026-04-08T18:00:00Z",
      "timeTo": "2026-04-08T23:00:00Z",
      "includeLineups": true,
      "includeTimeline": true,
      "includeStats": true,
      "includeWatchOptions": true
    }
  }
}

Quick rules

  • Keep windows bounded.
  • Preserve provider refs exactly as they came back.
  • Treat partial, missingSections, and limitations as first-class workflow signals.
  • Prefer atomic tools unless the product clearly benefits from a hybrid bundle.

Read this next