Fetch top News18 stories from its public RSS feed. Returns structured JSON for use in news aggregation and monitoring workflows.
Get News18 top stories. Returns fresh News18 top stories from its public 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?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions the source ('public RSS feed') and that stories are 'fresh', which gives some context. However, it does not describe the response format, pagination, limits, or any potential failure modes. For a simple retrieval tool this is adequate but not rich.
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 that clearly state the action and source. No fluff or repetition. Front-loaded with the primary purpose. Every word 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?
For a tool with no parameters and no output schema, the description covers the essentials: what it returns (top stories) and where they come from (public RSS feed). It is self-contained enough for an agent to call it correctly. Missing details like output structure are not critical given the simplicity.
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 is empty with zero parameters, so there is nothing to document. The baseline for 0 params is 4, and the description adds no unnecessary parameter information. The tool is callable without arguments, which the description does not confuse.
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 a specific resource ('News18 top stories'), and mentions the source ('public RSS feed'). Clear that it retrieves top stories from News18, but does not differentiate from sibling tools like news18_headlines, which likely cover similar content. Without contrast, an agent may struggle to choose between them.
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 tool versus alternatives. There is no mention of exclusions or conditions (e.g., 'use this for top stories, use news18_headlines for headlines'). The description simply states what it does, leaving the agent to infer usage from the name and siblings.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.