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

# Where Can I Watch This Game?

> Recommended Sports MCP workflow for normalized where-to-watch answers and program-linkage evidence.

# Where Can I Watch This Game?

Recommended path:

identify the right event -> `get_watch_availability`

## Pick the right surface

<Tabs>
  <Tab title="Normalized user-facing answer">
    Use [`get_watch_availability`](/sports-mcp-server/tool-reference/get_watch_availability) when the product needs a direct answer to where or whether the user can watch the selected sports entity.
  </Tab>

  <Tab title="Raw linkage evidence">
    Use [`list_programs_for_entity`](/sports-mcp-server/tool-reference/list_programs_for_entity) when product ops, QA, or editorial needs compact evidence rather than the normalized user-facing answer.
  </Tab>

  <Tab title="Program-first start">
    Use [`get_program_context`](/sports-mcp-server/tool-reference/get_program_context) when the product starts from a known program row instead of a sports entity.
  </Tab>
</Tabs>

## Variations

* If the event is ambiguous, use [`list_schedule`](/sports-mcp-server/tool-reference/list_schedule) to select the correct `eventId` first.
* If the product already knows the `eventId`, skip resolution and schedule browsing.
* If the product wants both normalized watchability and raw evidence, call the normalized tool first and use raw connectivity only for debugging or QA.

## Avoid

* using a GSD-only event response as a where-to-watch answer
* using raw linkage evidence when the experience really needs a normalized user-facing answer