Connectivity and Watchability Tools

​

Start Here If

• users ask “Where can I watch this?”
• you need to connect a match, team, venue, phase, or overall to related programs
• you already have a program ID and want to know what sports context it represents

​

Tool Selection Guide

​

Connectivity Tools

​

gns_related_programs_by_entity

• What it helps you do: find broadcast programs related to a sports entity.
• When to use it: a match, team, venue, phase, or overall is already known and the product wants the related program IDs.
• Inputs you need: entityId, optional language.
• What you get back: related program records and relationship metadata.
• Example user questions it can answer: “What broadcasts are related to this match?”
• Example request:

{
  "name": "gns_related_programs_by_entity",
  "arguments": {
    "entityId": "MATCH_ID",
    "language": "en-US"
  }
}

• Expected response summary: linked programs you can hand off to downstream broadcast or availability logic.
• What to call next: gns_watchability_by_entity if you want a more normalized shape.

​

gns_related_programs_by_program

• What it helps you do: move from a known program ID back to the sports entities it is linked to.
• When to use it: the user starts from a program or TV-guide context.
• Inputs you need: programId, optional language.
• What you get back: related sports entities and relationship metadata.
• Example user questions it can answer: “What game or event is this program tied to?”
• Example request:

{
  "name": "gns_related_programs_by_program",
  "arguments": {
    "programId": "PROGRAM_ID",
    "language": "en-US"
  }
}

• Expected response summary: entities such as matches, teams, phases, venues, or overalls related to the program.
• What to call next: gns_watchability_by_program or the relevant sports tool for the returned entity.

​

Watchability Bundles

​

gns_watchability_by_entity

• What it helps you do: normalize program linkage for a sports entity into a more AI-friendly watchability response.
• When to use it: you need cleaner, assistant-ready output than the raw connectivity response.
• Inputs you need: entityId, optional language.
• What you get back: normalized links plus the raw response payload.
• Example user questions it can answer: “Where can I watch this event?” and “Which broadcast cards should I show for this team?”
• Example request:

{
  "name": "gns_watchability_by_entity",
  "arguments": {
    "entityId": "MATCH_ID",
    "language": "en-US"
  }
}

• Expected response summary: a normalized list of linked programs with relation type and title fields that are easier to prompt against or render.
• What to call next: your product UI or any downstream program metadata workflow.

​

gns_watchability_by_program

• What it helps you do: normalize the reverse direction from program to sports entity.
• When to use it: a customer starts from a program and the product needs to explain the sports context behind it.
• Inputs you need: programId, optional language.
• What you get back: normalized entity linkage plus the raw response.
• Example user questions it can answer: “What sports event does this broadcast cover?”
• Example request:

{
  "name": "gns_watchability_by_program",
  "arguments": {
    "programId": "PROGRAM_ID",
    "language": "en-US"
  }
}

• Expected response summary: a clean set of related entities your product can turn into detail pages, assistant answers, or next-step tool calls.
• What to call next: gns_match_info, gns_phase_info, gns_overall_info, or gns_team_info, depending on the returned entity.

​

Recommended Pattern