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_phase_results
Family: Deep Sports Truth Tools
Return ordered phase or session results for qualifying, rounds, heats, groups, and similar staged competition slices.
- the host already knows the right
phaseId and needs the ordered result rows for that stage or session.
- Source ownership: GSD Lookup
Use something smaller or different when
- Do not use it as a replacement for the full schedule, standings, or one-event summary.
Plain-English prerequisites
- This tool does not require a prerequisite ID beyond the scoped inputs shown below.
| Input | What it means |
|---|
phaseId | Phase ref for the exact staged slice the host wants to inspect. |
| Input | What it means |
|---|
limit | Maximum number of rows to return. Keep it small for low-token UX and larger only when the UI truly needs a browse list. |
language | Optional 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 ordered phase or session results for qualifying, rounds, heats, groups, and similar staged competition slices.
Response shape
| Field | What it means |
|---|
data.phase | Normalized phase or session record. |
data.phasePayload | Raw provider phase payload for QA or advanced inspection. |
data.rows[] | Ordered normalized phase result rows. |
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_phase_results",
"arguments": {
"phaseId": "PHASE_ID",
"limit": 10
}
}
}
- Use
get_phase_results when the host already knows the right scope and needs this job directly.
Common mistakes
- Calling
get_phase_results before the host has the right provider refs or bounded window.
- Using
get_phase_results when a smaller sibling tool would answer the question more directly.
