Retrieve current NPR site-wide headlines from the public RSS feed. Get clean JSON data for news aggregation, monitoring, or analysis.
Get NPR site-wide headlines. Returns fresh headlines from NPR's 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 behavioral disclosure burden. It adds useful context by calling the feed 'public' (implying no auth) and 'fresh' (implying recency), and names the RSS source. It does not disclose output format, headline count, pagination, or rate limits, so transparency 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?
The description is two short sentences with the core action front-loaded. The second sentence adds source and freshness details, though 'site-wide' is repeated; overall there is no wasted content.
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, no-output-schema tool, the description covers the essential facts: what is returned, from where, and how fresh. It does not specify the response structure, but 'headlines' and 'RSS feed' give enough orientation for a simple 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 input schema has zero parameters, so there is nothing for the description to document. The baseline of 4 applies because no parameter semantics are needed.
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 uses the specific verb 'Get' with the resource 'NPR site-wide headlines' and identifies the source as NPR's public RSS feed. 'Site-wide' distinguishes it from more specific NPR tools like npr_article, npr_categories, or npr_topic, so an agent can tell what it returns.
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 description implies use when current, site-wide NPR headlines are needed, and the 'fresh' qualifier signals recency. It does not explicitly name alternatives or state when not to use it, leaving routing to sibling tools like npr_categories or npr_article to inference.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.