Fetch the four valid GhanaWeb TV video section values accepted by the videos endpoint, so you can query or filter video data correctly.
Get GhanaWeb TV video sections. Returns the complete four-value video category set accepted by ghanaweb-videos.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.17.7Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden, and it does disclose a meaningful behavioral trait: the result is a complete, fixed set of exactly four video categories rather than a dynamic or paginated list. It does not mention whether the values are stable identifiers or display labels, which is a minor gap.
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?
Two short sentences, front-loaded with the purpose and followed by the return contract. No filler, no repetition of the tool name or title.
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's disclosure of the four-value return set is exactly the compensating detail an agent needs. It omits nothing else critical for a zero-parameter lookup, though naming the four values would make it fully self-sufficient.
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 takes zero parameters, so there is nothing for the description to clarify beyond the schema; baseline 4 applies.
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 (Get) and resource (GhanaWeb TV video sections), and explicitly ties the resource to the sibling tool that consumes it ('accepted by ghanaweb-videos'). An agent can distinguish this from ghanaweb_videos and ghanaweb_video without opening any schema.
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 phrase 'accepted by ghanaweb-videos' strongly implies this is a discovery step that feeds the video-listing sibling, which is genuine usage context. It stops short of an explicit when-to-use vs when-not statement, so it does not reach 5.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.