Skip to main content

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.

Canonical tool name: list_programs_for_entity Family: Program Connectivity and Watchability Tools

​
What this tool is best at

Return compact raw evidence linking a sports entity to programs.

​
Choose this tool when

  • the host needs the raw graph before it normalizes watchability.
  • Source ownership: Dedicated availability primary when provisioned, otherwise fallback event/program evidence with explicit linkage limitations

​
Use something smaller or different when

  • the product wants a polished where-to-watch answer; use get_watch_availability 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

InputWhat it means
entityIdEntity ref for the selected sport, competition, season, event, participant, or venue. Use the same namespace you preserved from the earlier step.
entityTypeEntity kind for entityId. This tells the server which program-lookup parameters it should emit.

​
Optional inputs in the public contract

InputWhat it means
timeFromBounded window start. Use an ISO date or timestamp that matches the user’s browse moment or watchability horizon. Some tools require this field as part of the public contract.
timeToBounded window end. Keep it tight enough that the request still represents one real product moment. Some tools require this field as part of the public contract.
limitMaximum number of rows to return. Keep it small for low-token UX and larger only when the UI truly needs a browse list.
languageOptional BCP 47 language hint such as en-US. Use it when the host needs translated provider output.

​
Notes on optional inputs

  • timeFrom and timeTo are optional here. If you provide one, provide both so the linkage evidence remains bounded.

​
Sequencing guidance

Needed ID or scopeCall this firstThen use
scopeTool CatalogStart from the smallest tool that can safely anchor the workflow, then deepen only if the user asks for more.

​
Response highlights

  • Return compact raw evidence linking a sports entity to programs.

​
Response shape

FieldWhat it means
data.entityId / data.entityTypeEcho of the requested sports entity scope.
data.programs[]Program rows when dedicated entity-to-program linkage can be proven.
data.events[]Event evidence rows when only fallback evidence exists.
data.availabilityModeWhether the answer is using dedicated linkage, evidence-only fallback, or no linkage.

​
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

{
  "jsonrpc": "2.0",
  "id": "tool-call-1",
  "method": "tools/call",
  "params": {
    "name": "list_programs_for_entity",
    "arguments": {
      "entityId": "ON_EVENT_GID",
      "entityType": "event",
      "timeFrom": "2026-04-08",
      "timeTo": "2026-04-09"
    }
  }
}

​
Previous-step tools

​
Next-step tools

​
Alternative tools

  • No common alternatives.

​
Prompt patterns this tool fits

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

​
Common mistakes

  • Calling list_programs_for_entity before the host has the right provider refs or bounded window.
  • Using list_programs_for_entity when a smaller sibling tool would answer the question more directly.