Retrieve current stories from GhanaWeb with headlines, canonical article URLs, and publication times to track news without extra fields.
Get GhanaWeb latest stories. Lists GhanaWeb's current stories across the site, with no parameters. Each item carries its headline as title, the canonical article url and the published_at time. No author, summary or image is returned.
| 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 and does disclose the exact response shape (title, url, published_at) plus negative constraints ('No author, summary or image is returned'), which is genuinely useful for planning. It omits ordering, item count, and pagination/refresh behavior, so it stops short of full transparency.
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 sentences, front-loaded with the verb and resource, then scope, then return fields and exclusions. Nothing is redundant and the negative information about omitted fields earns its place.
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?
There is no output schema, so the description must describe returns, and it does so field-by-field. For a zero-parameter feed it is nearly complete, with only ordering/pagination left unstated.
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?
There are zero parameters, so the baseline is 4; the description reinforces this with 'with no parameters'. No further parameter semantics are needed or expected.
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 'Lists GhanaWeb's current stories across the site'. The scope is clear (site-wide current stories), but it never distinguishes itself from close siblings like ghanaweb_headlines or ghanaweb_archive, so an agent must guess which feed to pick.
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 'current stories across the site' implies the use case (site-wide latest feed), but there is no explicit when-to-use, no when-not-to-use, and no named alternative such as ghanaweb_headlines. Usage is only inferable.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.