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

# Get Participant Profile

> Return team, person, or university profile data with normalized refs and optional season context.

Canonical tool name: `get_participant_profile`

Family: [Deep Sports Truth Tools](/sports-mcp-server/tools/deep-sports-truth-tools)

## What this tool is best at

Return team, person, or university profile data with normalized refs and optional season context.

## Choose this tool when

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

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

| Input           | What it means                                                |
| --------------- | ------------------------------------------------------------ |
| `participantId` | Participant ref for the subject team, person, or university. |

### Optional inputs in the public contract

| 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](/sports-mcp-server/tools/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

<CodeGroup>
  ```json JSON-RPC theme={null}
  {
    "jsonrpc": "2.0",
    "id": "tool-call-1",
    "method": "tools/call",
    "params": {
      "name": "get_participant_profile",
      "arguments": {
        "participantId": "TEAM_ID",
        "participantType": "team"
      }
    }
  }
  ```

  ```bash curl theme={null}
  curl "https://sports-mcp-server.etonecarg.com/" \
    -X POST \
    -H "Authorization: Bearer $SPORTS_MCP_API_KEY" \
    -H "Accept: application/json, text/event-stream" \
    -H "Content-Type: application/json" \
    -H "mcp-protocol-version: 2025-03-26" \
    -d '{
    "jsonrpc": "2.0",
    "id": "tool-call-1",
    "method": "tools/call",
    "params": {
      "name": "get_participant_profile",
      "arguments": {
        "participantId": "TEAM_ID",
        "participantType": "team"
      }
    }
  }'
  ```

  ```ts TypeScript theme={null}
  const payload = {
      "jsonrpc": "2.0",
      "id": "tool-call-1",
      "method": "tools/call",
      "params": {
        "name": "get_participant_profile",
        "arguments": {
          "participantId": "TEAM_ID",
          "participantType": "team"
        }
      }
    };

  const response = await fetch("https://sports-mcp-server.etonecarg.com/", {
    method: "POST",
    headers: {
      Authorization: `Bearer ${process.env.SPORTS_MCP_API_KEY!}`,
      Accept: "application/json, text/event-stream",
      "Content-Type": "application/json",
      "mcp-protocol-version": "2025-03-26",
    },
    body: JSON.stringify(payload),
  });

  const data = await response.json();
  console.log(JSON.stringify(data, null, 2));
  ```

  ```python Python theme={null}
  import json
  import os

  import requests

  payload = {
    "jsonrpc": "2.0",
    "id": "tool-call-1",
    "method": "tools/call",
    "params": {
      "name": "get_participant_profile",
      "arguments": {
        "participantId": "TEAM_ID",
        "participantType": "team"
      }
    }
  }

  response = requests.post(
      "https://sports-mcp-server.etonecarg.com/",
      headers={
          "Authorization": f"Bearer {os.environ['SPORTS_MCP_API_KEY']}",
          "Accept": "application/json, text/event-stream",
          "Content-Type": "application/json",
          "mcp-protocol-version": "2025-03-26",
      },
      json=payload,
      timeout=30,
  )

  response.raise_for_status()
  print(json.dumps(response.json(), indent=2))
  ```
</CodeGroup>

## Related tools

### Previous-step tools

* [`resolve_entities`](/sports-mcp-server/tool-reference/resolve_entities)
* [`get_event_lineups`](/sports-mcp-server/tool-reference/get_event_lineups)

### Next-step tools

* [`get_roster`](/sports-mcp-server/tool-reference/get_roster)
* [`get_media_assets`](/sports-mcp-server/tool-reference/get_media_assets)

### Alternative tools

* No common alternatives.

## Prompt patterns this tool fits

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