Fetch the current Yahoo Sports TV program schedule to see what is airing now. Use it for quick schedule lookups without date, league, or pagination inputs.
Yahoo Sports TV schedule. Returns the current program schedule exposed by Yahoo Sports' Watch page. The source request has no date, league, season, sort, or pagination parameter.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.17.18Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It usefully discloses that the request is unfilterable and returns only the 'current' schedule, which tells the agent it cannot scope or page results, but it says nothing about freshness, coverage window, or return volume.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three short sentences, front-loaded with the resource identity and followed by scope and constraint. Little waste, though 'Returns the current program schedule exposed by Yahoo Sports' Watch page' partially restates the opening line.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
No output schema exists, so the description should hint at what a 'program schedule' entry contains (times, channels, events). It names the resource but leaves the payload shape entirely unspecified for a tool whose value depends on knowing what programs and broadcast details come back.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Zero parameters, so baseline 4 applies. The explicit note that no date/league/season/sort/pagination parameter exists is mildly redundant with an empty schema but still prevents an agent from attempting filter arguments.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb+resource: it returns the current TV program schedule from Yahoo Sports' Watch page. It implicitly separates itself from the many date/league-scoped siblings (yahoo_sports_league_schedule, yahoo_sports_golf_schedule) by calling this a 'TV' schedule, but never names those siblings explicitly.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Usage is only implied through the constraint that there is no date, league, season, sort, or pagination parameter, so an agent infers this is a fixed current-snapshot listing. There is no explicit statement of when to choose this over the schedule_catalog or league schedule siblings.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.