> ## 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 Else Should I Watch?

> Recommended Sports MCP workflow for watchability candidate-set prompts where the host ranks or curates the final results.

# What Else Should I Watch?

Recommended path:

`resolve_entities` or `get_program_context` -> `list_watchable_schedule` or `list_programs_for_entity` -> host ranking/curation -> `get_watch_availability`

## Choose the right seed

<Tabs>
  <Tab title="Sports entity seed">
    Use [`resolve_entities`](/sports-mcp-server/tool-reference/resolve_entities) only if the competition, participant, or event is still ambiguous, then pass the best provider ref into [`list_watchable_schedule`](/sports-mcp-server/tool-reference/list_watchable_schedule) for a bounded candidate set.
  </Tab>

  <Tab title="Program seed">
    Start from [`get_program_context`](/sports-mcp-server/tool-reference/get_program_context) when the user begins with a known program row or channel tile, then use the linked sports context to choose the next candidate-set call.
  </Tab>

  <Tab title="Selected recommendation">
    After the host or user chooses one candidate, move into [`get_watch_availability`](/sports-mcp-server/tool-reference/get_watch_availability) for the normalized where-to-watch answer.
  </Tab>
</Tabs>

## Variations

* Use [`list_programs_for_entity`](/sports-mcp-server/tool-reference/list_programs_for_entity) or [`list_entities_for_program`](/sports-mcp-server/tool-reference/list_entities_for_program) when QA needs raw linkage evidence.
* Keep the candidate-set window bounded to the actual UX moment.
* If the product already knows the exact event it wants, skip candidate ranking and answer directly.

## Avoid

* expecting the server to perform editorial or personalized recommendation ranking by itself
* using a deep sports tool alone when the real job is to assemble a watchable candidate set