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

# Hybrid Bundle Tools

> Use composed tools when the product needs both deep sports truth and program-aware availability in one answer.

Use composed tools when the product needs both deep sports truth and program-aware availability in one answer.

Use this family when the workflow fits this source-ownership boundary. Move to the tool page once you know the exact job and scope.

## Sequencing habits

* Use bundles only when the product benefits from one coherent surface.
* Read `partial`, `missingSections`, and `limitations` before rendering as complete.

## Decision guide

| Tool                                                                           | What it helps with                                                                                                                                                                           | Primary data source(s)                                                           |
| ------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------- |
| [`get_competition_hub`](/sports-mcp-server/tool-reference/get_competition_hub) | Return structure, schedule, standings, rankings, and optional watchable rail for one competition scope.                                                                                      | GSD Lookup primary, availability overlay optional                                |
| [`get_series_hub`](/sports-mcp-server/tool-reference/get_series_hub)           | Return one compact series bundle with series seasons, bounded event rows, leaderboard refs, and phase refs for tours and motorsports.                                                        | GSD Lookup primary                                                               |
| [`get_event_center`](/sports-mcp-server/tool-reference/get_event_center)       | Return the main one-call event recap bundle with summary, optional lineups, optional timeline, optional stats, optional odds, optional watchability, optional media, and optional editorial. | GSD Lookup primary, availability optional, GSD Metadata media/editorial optional |

## Tool-by-tool guidance

### [`get_competition_hub`](/sports-mcp-server/tool-reference/get_competition_hub)

* Job: Return structure, schedule, standings, rankings, and optional watchable rail for one competition scope.
* Source ownership: GSD Lookup primary, availability overlay optional
* Use it when: the product needs one coherent competition surface instead of stitching multiple calls together.
* Do not use it when: the host only needs a single atomic section like standings or a single schedule list.

### [`get_series_hub`](/sports-mcp-server/tool-reference/get_series_hub)

* Job: Return one compact series bundle with series seasons, bounded event rows, leaderboard refs, and phase refs for tours and motorsports.
* Source ownership: GSD Lookup primary
* Use it when: the product needs one tour or series surface instead of stitching schedule, rankings, and phase discovery together.
* Do not use it when: the host only needs a single schedule list, one leaderboard, or one phase/session result slice.

### [`get_event_center`](/sports-mcp-server/tool-reference/get_event_center)

* Job: Return the main one-call event recap bundle with summary, optional lineups, optional timeline, optional stats, optional odds, optional watchability, optional media, and optional editorial.
* Source ownership: GSD Lookup primary, availability optional, GSD Metadata media/editorial optional
* Use it when: the product wants the event center in one response instead of calling summary, lineups, timeline, stats, odds, watchability, and media separately.
* Do not use it when: the host only needs one atomic event section or when the extra sections would waste tokens.

## Next steps

* Use [Tool Catalog](/sports-mcp-server/tools/tool-catalog) when you want the full 1.4.1 surface in one place.
* Use [ID Acquisition and Tool Sequencing](/sports-mcp-server/tools/id-acquisition-and-tool-sequencing) when the host still needs provider refs or a safer tool order.
* Use [Prompt-to-Tool Mapping](/sports-mcp-server/prompt-to-tool-mapping) when you want a proven low-token workflow for a real user prompt.