Skip to main content
Canonical tool name: get_watch_availability Family: Program Connectivity and Watchability Tools

What this tool is best at

Return the normalized where-to-watch answer for a sports entity in a bounded window, with proven or evidence-only watchability semantics.

Choose this tool when

  • the host needs a direct answer to where, whether, or on what service/channel the user can watch a sports entity.
  • Source ownership: Dedicated availability primary when provisioned, otherwise evidence-only watchability fallback

Use something smaller or different when

  • Do not use it as a substitute for deep sports detail or as a raw linkage-inspection tool when QA needs the underlying evidence graph instead.

Inputs you need

Plain-English prerequisites

  • This tool does not require a prerequisite ID beyond the scoped inputs shown below.

Required inputs in the public contract

Optional inputs in the public contract

Sequencing guidance

Response highlights

  • data.options[] is the normalized watchability answer when channels or services can be grounded.
  • data.eventEvidence[] carries fallback event evidence when the server cannot prove channel or service linkage.
  • data.linkageStatus and data.availabilityMode tell the host whether the answer is proven, unresolved, or unavailable.

Response shape

Reuse next

  • Reuse provider refs returned by this tool to avoid resolving the same entity again.
  • Read meta.agentHints.recommendedNextTools and meta.agentHints.disambiguationOptions as non-binding host hints.

Example requests

Previous-step tools

Next-step tools

Alternative tools

  • No common alternatives.

Prompt patterns this tool fits

  • Use get_watch_availability when the host already knows the right scope and needs this job directly.

Common mistakes

  • Expecting channels or services to appear when the response is in evidence-only fallback mode.
  • Treating fallback event evidence as if it were proven where-to-watch availability.