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_competition_structure Family: Resolution and Scope Tools

​
What this tool is best at

Return normalized competition structure and hierarchy for a league or competition season.

​
Choose this tool when

  • the host needs the tournament tree, phase layout, or season hierarchy before calling deeper tools.
  • Source ownership: GSD Lookup primary

​
Use something smaller or different when

  • Do not use it if the product only needs current standings, one event, or watchability.

​
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

  • None.

​
Optional inputs in the public contract

InputWhat it means
competitionIdGSD-facing competition ref when the host wants the broader competition hierarchy.
competitionSeasonIdGSD-facing season ref when the host wants the exact season structure and phase layout.
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 normalized competition structure and hierarchy for a league or competition season.

​
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_competition_structure",
    "arguments": {
      "competitionId": "LEAGUE_ID"
    }
  }
}

​
Previous-step tools

​
Next-step tools

​
Alternative tools

  • No common alternatives.

​
Prompt patterns this tool fits

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

​
Common mistakes

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