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_participant_profile
Family: Deep Sports Truth Tools
Return team, person, or university profile data with normalized refs and optional season context.
- Use it for team hubs, player hubs, and participant identity pages.
- Source ownership: GSD Lookup primary, On Universities enrichment optional
Use something smaller or different when
- the host only needs a roster list or one event’s lineups/stat line.
Plain-English prerequisites
- This tool does not require a prerequisite ID beyond the scoped inputs shown below.
| Input | What it means |
|---|
participantId | Participant ref for the subject team, person, or university. |
| Input | What it means |
|---|
participantType | Participant kind for profile requests. Set this explicitly when your host already knows whether the subject is a team, person, or university. |
competitionId | Optional competition ref that asks the server for broader competition context around the participant. |
competitionSeasonId | Optional season ref when the profile should be anchored to one specific season. |
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 team, person, or university profile data with normalized refs and optional season 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
{
"jsonrpc": "2.0",
"id": "tool-call-1",
"method": "tools/call",
"params": {
"name": "get_participant_profile",
"arguments": {
"participantId": "TEAM_ID",
"participantType": "team"
}
}
}
- Use
get_participant_profile when the host already knows the right scope and needs this job directly.
Common mistakes
- Calling
get_participant_profile before the host has the right provider refs or bounded window.
- Using
get_participant_profile when a smaller sibling tool would answer the question more directly.
