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_roster
Family: Deep Sports Truth Tools
Return roster data for a team inside one competition context.
the host needs the season-context roster and not just a single-event lineup.
Source ownership: GSD Lookup
Use something smaller or different when
Do not use it for people stats, lineups, or general team identity questions.
Plain-English prerequisites
competitionId / competitionSeasonId: Provide one competition context in addition to participantId; the roster contract is season- or competition-specific.
Input What it means participantIdProvider ref for one team, person, or university-linked participant. Preserve the original namespace from the resolving step.
Input What it means 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. languageOptional BCP 47 language hint such as en-US. Use it when the host needs translated provider output.
Sequencing guidance Needed ID or scope Call this first Then use scope Tool Catalog Start from the smallest tool that can safely anchor the workflow, then deepen only if the user asks for more.
Response highlights
Return roster data for a team inside one competition context.
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 JSON-RPC
curl
TypeScript
Python
{ "jsonrpc" : "2.0" , "id" : "tool-call-1" , "method" : "tools/call" , "params" : { "name" : "get_roster" , "arguments" : { "participantId" : "TEAM_ID" , "competitionId" : "LEAGUE_ID" } } }
Use get_roster when the host already knows the right scope and needs this job directly.
Common mistakes
Calling get_roster before the host has the right provider refs or bounded window.
Using get_roster when a smaller sibling tool would answer the question more directly.
