Fetch NBC News top stories from the public RSS feed and receive clean JSON for integration.
Get NBC News top stories. Returns fresh NBC News top 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?
With no annotations, the description carries the full burden. It discloses the source (public RSS feed) and that stories are 'fresh', which adds context beyond a generic fetch. However, it does not mention caching, rate limits, or response format, so it is only moderately transparent.
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?
A single, concise sentence that front-loads the main action and resource, then adds the source detail. No wasted words.
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 simple tool with no parameters, no output schema, and no annotations, the description is largely complete. It tells the agent what is returned and from where. Minor gaps like potential limits or response format are not critical for a straightforward top-stories fetch.
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 has zero parameters, so there is nothing to explain. Per the baseline rule for 0 params, a score of 4 is appropriate since the description does not need to compensate for missing schema details.
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 verb 'Get' and resource 'NBC News top stories', and clarifies it comes from the public site-wide RSS feed. This distinguishes it from sibling tools like nbc_headlines or nbc_sections by focusing on top stories rather than headlines or 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 is given on when to use this tool versus alternatives such as nbc_headlines, nbc_article, or nbc_sections. There are many NBC-related siblings, and the description does not mention any conditions or exclusions, leaving the agent to infer the appropriate context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.