Fetch GhanaWeb public news stories from its Google News sitemap, returning canonical URLs, headlines, and publication times.
Get GhanaWeb latest stories. Returns GhanaWeb's current public stories from its Google News sitemap, including canonical URL, headline, and publication time.
| 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, the description carries the full burden. It helpfully discloses the data source (Google News sitemap) and that the stories are 'current public' ones, but says nothing about result limits, pagination, or update cadence for a feed-style endpoint.
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 tight sentences with the core action front-loaded and the return shape stated second. No filler or 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?
For a parameterless, read-only feed with no output schema, the description covers purpose, source, and returned fields adequately. The only missing piece is how it relates to sibling GhanaWeb feed tools.
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 per the rubric this is a baseline 4. The description adds the return-field context (canonical URL, headline, publication time), though the schema has nothing to document.
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 ('Get GhanaWeb latest stories') and names the retrieval source (Google News sitemap). It distinguishes the tool from the article/archive siblings implicitly via 'latest', though it never explicitly contrasts with ghanaweb_headlines or ghanaweb_sections.
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?
No guidance on when to use this versus ghanaweb_headlines, ghanaweb_article, ghanaweb_archive, or the other GhanaWeb siblings. The agent is left to infer that this returns the current feed rather than a filtered or historical query.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.