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_rankings Family: Deep Sports Truth Tools

What this tool is best at

Return the richest non-empty leaderboard rows for a competition or series scope, plus selection metadata.

Choose this tool when

  • the host needs leaderboards, driver standings, golf leaderboards, or category rankings rather than a single standings table.
  • Source ownership: GSD Lookup

Use something smaller or different when

  • Do not use it to replace standings, one-event stats, or phase/session results.

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
classificationIdProvider ref for one rankings or classification view when the host already knows the exact leaderboard object it needs.
overallIdProvider ref for one leaderboard or overall table view when the host already knows the exact result object it needs.
competitionIdProvider ref for one competition scope. Match the namespace to the tool family: GSD refs for sports-truth tools, On refs for watchability-first tools.
competitionSeasonIdProvider ref for one competition season. Use it when the host needs a season-specific table, ranking, structure, or roster context.
seriesIdProvider ref for one cross-competition series or tour scope such as Formula 1, ATP, PGA Tour, or LPGA Tour.
seriesSeasonIdProvider ref for one series season. Use it when the host needs one tour season instead of the broader series.
limitMaximum number of rows to return. Keep it small for low-token UX and larger only when the UI truly needs a browse list.
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

  • Raw rankings payload from the selected scope or ranking ref.
  • Normalized rows, rowCount, additive selectedRef, selectedRefId, selectedRefType, and rowsSourcePath fields.
  • Deterministic selection of the richest non-empty leaderboard collection instead of trusting the first ref.

Response shape

FieldWhat it means
data.rankingsRaw ranking payload selected for the answer.
data.rows[]Normalized leaderboard rows.
data.rowCountNumber of normalized leaderboard rows available before truncation.
data.selectedRefId / data.selectedRefType / data.selectedRefDeterministic ranking-selection metadata for deepening and QA.
data.rowsSourcePathSource-path hint describing where the selected rows came from.

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_rankings",
    "arguments": {
      "competitionId": "LEAGUE_ID",
      "limit": 10
    }
  }
}

Previous-step tools

Next-step tools

Alternative tools

  • No common alternatives.

Prompt patterns this tool fits

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

Common mistakes

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