mpaz_list_videosLists games with NFHS Network broadcast links, giving you direct access to watch each game's stream.
Games with a broadcast link. These are NFHS Network links rather than hosted clips, so videoLengthSeconds is 0 on every entry and title is the team name — that is expected, not missing data. Read-only.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.0.0Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"v0.2.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description discloses non-obvious data quirks: videoLengthSeconds is always 0 and title contains the team name, not a video title, and explicitly says this is expected rather than missing data. This adds real value beyond the readOnlyHint annotation.
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?
The description is short and front-loaded with the core purpose, then quickly explains the two important output quirks and confirms read-only behavior. Every sentence adds necessary information without redundancy.
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?
With no input parameters and no output schema, the description covers the most likely sources of agent confusion by flagging the unusual field semantics. It does not enumerate the full item shape, but the key surprises are handled sufficiently for a simple list operation.
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?
The tool has zero parameters, so the baseline of 4 applies. The description adds nothing about parameters, but none are needed since the input schema is empty.
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?
The title and description both state a specific verb and resource: list games that have broadcast links. The description further clarifies that these are NFHS Network links rather than hosted clips, distinguishing the resource from a generic video listing.
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?
The description clearly implies this tool is for retrieving games with broadcast links, and the read-only note gives agent confidence about side effects. There are no sibling tools covering the same broadcast-link function, so explicit alternative routing is not needed.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.