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

# Catch Me Up on This Game

> Recommended Sports MCP workflow for game recap, catch-up, and event-center prompts.

# Catch Me Up on This Game

Recommended path:

`resolve_entities` when needed -> `list_schedule` -> `get_event_summary` or `get_event_center`

## Choose the right depth

<Tabs>
  <Tab title="Fast recap">
    Use [`get_event_summary`](/sports-mcp-server/tool-reference/get_event_summary) when the UX needs the smallest sufficient answer for one event.
  </Tab>

  <Tab title="Event-center recap">
    Use [`get_event_center`](/sports-mcp-server/tool-reference/get_event_center) when the experience benefits from summary, lineups, timeline, stats, watchability, and media in one response.
  </Tab>

  <Tab title="Action-by-action">
    Add [`get_event_timeline`](/sports-mcp-server/tool-reference/get_event_timeline) only when the recap needs explicit play-by-play or incident-level evidence.
  </Tab>
</Tabs>

## Variations

* If the host already knows the `eventId`, skip resolution and schedule selection.
* If the recap is stats-heavy, add [`get_event_stats`](/sports-mcp-server/tool-reference/get_event_stats).
* If the recap should answer where-to-watch next, branch into [`get_watch_availability`](/sports-mcp-server/tool-reference/get_watch_availability) after the event is identified.

## Avoid

* starting with a watchability tool when the user really wants sports truth
* using a broad live slate when the product already knows the specific event