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.

Canonical tool name: get_event_lineups Family: Deep Sports Truth Tools

What this tool is best at

Return lineups and officials for one event.

Choose this tool when

  • the answer needs the people on the field, court, grid, or match sheet.
  • Source ownership: GSD Lookup

Use something smaller or different when

  • Do not use it as a general event summary or a substitute for stats or actions.

Inputs you need

Plain-English prerequisites

  • This tool does not require a prerequisite ID beyond the scoped inputs shown below.

Required inputs in the public contract

InputWhat it means
eventIdProvider ref for one event. Prefer the GSD-facing event ref for deep-sports tools and the selected event row for hybrid follow-ons.

Optional inputs in the public contract

InputWhat it means
idSourceLookup-path hint for the supplied ID. auto uses namespace-aware routing, gsd treats the ID as sports-truth-facing, and on treats it as On-facing. It does not change source-of-truth ownership.
languageOptional BCP 47 language hint such as en-US. Use it when the host needs translated provider output.

Sequencing guidance

Needed ID or scopeCall this firstThen use
scopeTool CatalogStart from the smallest tool that can safely anchor the workflow, then deepen only if the user asks for more.

Response highlights

  • Return lineups and officials for one event.

Reuse next

  • Reuse provider refs returned by this tool to avoid resolving the same entity again.
  • Read meta.agentHints.recommendedNextTools and meta.agentHints.disambiguationOptions as non-binding host hints.

Example requests

{
  "jsonrpc": "2.0",
  "id": "tool-call-1",
  "method": "tools/call",
  "params": {
    "name": "get_event_lineups",
    "arguments": {
      "eventId": "MATCH_ID"
    }
  }
}

Previous-step tools

Next-step tools

Alternative tools

  • No common alternatives.

Prompt patterns this tool fits

  • Use get_event_lineups when the host already knows the right scope and needs this job directly.

Common mistakes

  • Calling get_event_lineups before the host has the right provider refs or bounded window.
  • Using get_event_lineups when a smaller sibling tool would answer the question more directly.