> ## 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.

# Tell Me About This Team or Player

> Recommended Sports MCP workflow for participant-centric prompts.

# Tell Me About This Team or Player

Recommended path:

`resolve_entities` when needed -> `get_participant_profile`

## Then branch by what the user means

<Tabs>
  <Tab title="Identity and overview">
    Stay with [`get_participant_profile`](/sports-mcp-server/tool-reference/get_participant_profile) when the user needs the participant's identity, context, and season-aware profile surface.
  </Tab>

  <Tab title="Roster depth">
    Add [`get_roster`](/sports-mcp-server/tool-reference/get_roster) when the product needs who is on the team inside a competition context.
  </Tab>

  <Tab title="Upcoming or watchable games">
    Use [`list_schedule`](/sports-mcp-server/tool-reference/list_schedule) for sports-truth schedule flows or [`list_watchable_schedule`](/sports-mcp-server/tool-reference/list_watchable_schedule) for watchability-first browse flows.
  </Tab>
</Tabs>

## Variations

* Use [`get_event_stats`](/sports-mcp-server/tool-reference/get_event_stats) when the user is really asking about one performance in one event.
* Use [`get_media_assets`](/sports-mcp-server/tool-reference/get_media_assets) when the product needs logos, headshots, or imagery.
* Keep `participantType` accurate when you already know whether the subject is a team, person, or university.

## Avoid

* using [`get_watch_availability`](/sports-mcp-server/tool-reference/get_watch_availability) as the first profile tool
* using [`get_competition_hub`](/sports-mcp-server/tool-reference/get_competition_hub) when the prompt is clearly participant-led