List GDELT TV 2.0 AI stations with IDs and labels to use as station parameters in GDELT TV endpoints.
List GDELT Television 2.0 AI stations. Lists the television stations GDELT currently monitors, each with its id, short label and a label_long that includes its coverage dates. Use the ids as station in the GDELT TV endpoints. It takes no parameters.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.16.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations, so the description carries the full burden. It discloses the return fields and that no parameters are taken (read-only nature implied by 'List'), but says nothing about result stability, pagination, or whether the station list changes over time.
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 purpose. Slight redundancy in the opening ('List ... Lists ...'), but overall efficient with no filler.
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 output schema, annotations, or parameters, the description does the necessary work: it explains the purpose, the shape of items returned, and how the ids feed downstream TV endpoints. Only the safety/pagination details are absent, which for a static enumeration is minor.
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 is 4. The statement 'It takes no parameters' merely restates the empty schema and adds no meaning beyond it.
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 and resource ('List GDELT Television 2.0 AI stations') and details the returned fields (id, label, label_long with coverage dates). It does not name a sibling to differentiate from, but the tool's role is unambiguous.
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?
Explicitly tells the agent how to use the output: 'Use the ids as `station` in the GDELT TV endpoints', which positions the tool as a prerequisite lookup for the TV family. No explicit when-not guidance, but the discovery role is clear.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.