Fetch top Vanguard Nigeria stories from the public RSS feed. Get current headlines as clean JSON for news monitoring and integration.
Get Vanguard top stories. Returns fresh Vanguard (Nigeria) stories from the public site-wide RSS feed.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.17.5Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
There are no annotations, so the description carries the burden of behavioral disclosure. It does add useful context by describing the source as a public, site-wide, fresh RSS feed, which implies no authentication and a broad unfiltered source. It does not disclose ordering, result limits, or the shape of the returned stories, but for a simple zero-parameter feed this is a reasonable baseline.
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 two short sentences with no filler. The primary action is front-loaded, and the second sentence adds just enough clarifying detail about the source and scope.
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 zero-parameter RSS news-list tool with no output schema, the description provides enough to invoke the tool correctly: what it returns, how fresh it is, and where the data comes from. It is slightly light on return-value details, but the low complexity and empty schema reduce the need for more.
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 input schema has zero parameters, so the description cannot meaningfully add parameter-level detail. The no-parameter baseline applies, and the description's focus on source and content is sufficient.
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 description states a specific action and resource: 'Get Vanguard top stories,' with useful context that these are fresh Nigeria stories from the public site-wide RSS feed. It is clearly about retrieving Vanguard news, though it does not explicitly distinguish itself from sibling tools like vanguardng_headlines or vanguardng_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?
Usage is implied: use this when you want top/fresh Vanguard stories. However, there is no explicit guidance about when to prefer this over alternatives such as vanguardng_headlines, vanguardng_article, or vanguardng_sections, and no exclusions are mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.