> ## 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 Does the League or Tournament Picture Look Like?

> Recommended Sports MCP workflow for competition overview, table, bracket, and tournament-picture prompts.

# What Does the League or Tournament Picture Look Like?

Recommended path:

`resolve_entities` when needed -> `get_competition_hub`

## Then deepen only when needed

<Tabs>
  <Tab title="One coherent overview">
    Use [`get_competition_hub`](/sports-mcp-server/tool-reference/get_competition_hub) when the UX needs structure, standings, rankings, schedule slice, and optional watchable rail in one response.
  </Tab>

  <Tab title="Standings-heavy">
    Add [`get_standings`](/sports-mcp-server/tool-reference/get_standings) when the product needs a tighter table-first answer.
  </Tab>

  <Tab title="Bracket or phase-heavy">
    Add [`get_competition_structure`](/sports-mcp-server/tool-reference/get_competition_structure) when the experience is especially bracket-, phase-, or tournament-tree oriented.
  </Tab>
</Tabs>

## Variations

* Add [`list_schedule`](/sports-mcp-server/tool-reference/list_schedule) when the question includes “today,” “this week,” or “next round.”
* Add [`list_watchable_schedule`](/sports-mcp-server/tool-reference/list_watchable_schedule) when the product needs a watchable rail next to the competition picture.
* Add [`get_rankings`](/sports-mcp-server/tool-reference/get_rankings) when the UX is leaderboard-led rather than table-led.

## Avoid

* using watchability-first tools to answer pure standings or rankings questions
* reaching for a bundle if the user only wants one atomic section