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

# What Happened This Season or How Does It Compare Historically?

> Recommended Sports MCP workflow for season recap, historical framing, and host-owned comparison prompts.

# What Happened This Season or How Does It Compare Historically?

Recommended path:

`resolve_entities` when needed -> `get_competition_hub` -> atomic follow-ons when necessary

## Choose the right compare pattern

<Tabs>
  <Tab title="Season recap">
    Use [`get_competition_hub`](/sports-mcp-server/tool-reference/get_competition_hub) for the fastest season-shaped overview.
  </Tab>

  <Tab title="Table or leaderboard detail">
    Add [`get_standings`](/sports-mcp-server/tool-reference/get_standings) or [`get_rankings`](/sports-mcp-server/tool-reference/get_rankings) when the answer should stay tighter than the full hub.
  </Tab>

  <Tab title="Historical comparison">
    Call the smallest relevant tools multiple times and compare the results in the host or agent. Sports MCP Server intentionally does not expose one public compare tool.
  </Tab>
</Tabs>

## Low-token comparison recipes

* season vs previous season: call [`get_competition_hub`](/sports-mcp-server/tool-reference/get_competition_hub) twice
* team vs team: call [`get_participant_profile`](/sports-mcp-server/tool-reference/get_participant_profile) for each team and add shared standings context
* player vs player: call [`get_participant_profile`](/sports-mcp-server/tool-reference/get_participant_profile) for each player and add event stats when needed
* event vs event: call [`get_event_center`](/sports-mcp-server/tool-reference/get_event_center) for each event

## Avoid

* expecting one public compare tool
* using watchability-first tools for purely historical sports questions