> ## 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 Is On Today?

> Recommended Sports MCP workflow for today, tonight, and live-slate prompts.

# What Is On Today?

Recommended path:

`resolve_entities` when needed -> `list_watchable_schedule` -> `list_live_slate` or `list_schedule`

## Pick the branch that matches the UX

<Tabs>
  <Tab title="Watchability-first">
    Start with [`list_watchable_schedule`](/sports-mcp-server/tool-reference/list_watchable_schedule) when the real job is what the user can watch in a bounded window.

    Then:

    * use [`list_live_slate`](/sports-mcp-server/tool-reference/list_live_slate) if the UX needs now-playing or imminently-live context
    * use [`get_watch_availability`](/sports-mcp-server/tool-reference/get_watch_availability) for a selected row
  </Tab>

  <Tab title="Competition-first">
    Start with [`list_schedule`](/sports-mcp-server/tool-reference/list_schedule) when the question is really about the sports calendar rather than watchability.

    Then:

    * use [`get_event_summary`](/sports-mcp-server/tool-reference/get_event_summary) or [`get_event_center`](/sports-mcp-server/tool-reference/get_event_center) if the user drills into one event
  </Tab>
</Tabs>

## Variations

* If the user starts with a competition, resolve first only if your host does not already have the correct provider ref.
* If the product begins with a home-page rail, use a tighter window than “today” when possible.
* If the product needs to compare sports-truth rows against watchable rows, do it in the host instead of pretending the two schedule tools are interchangeable.

## Avoid

* treating [`list_schedule`](/sports-mcp-server/tool-reference/list_schedule) as a watchability tool
* treating [`list_watchable_schedule`](/sports-mcp-server/tool-reference/list_watchable_schedule) as a substitute for standings or event detail