Retrieve public NPR stories from a section archive page by section slug; use npr-categories for valid slugs.
Get NPR section headlines. Returns the newest public NPR stories from one section archive page. topic is a section slug; use npr-categories for the current value space.
| Name | Required | Description | Default |
|---|---|---|---|
| topic | Yes | NPR section slug |
Changes observed during successful MCP inspections.
v1.17.5Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations exist, so the description carries the burden. It discloses that it returns only public stories, implying content availability, but lacks details on pagination or output structure. The mention of 'archive page' hints at scope but is not fully explicit.
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 sentences with essential information; the first states the function, the second adds input guidance. No redundancy and the key message is front-loaded.
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 single-parameter tool with no output schema or annotations, the description covers the core functionality and the key input source. Minor ambiguity exists between 'headlines' and 'stories,' but overall it's sufficient for an agent to call it correctly.
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 schema already documents topic as a slug, but the description adds that npr-categories provides the current value space, which is actionable guidance beyond the schema. This adds meaning beyond the raw schema description.
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-resource pair (Get NPR section headlines) and clarifies it returns the newest stories from an archive page, distinguishing it from general headline tools like npr_headlines. The mention of 'section' and 'archive page' gives precise scope.
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?
Provides clear guidance on the input: topic is a slug and explicitly points to npr-categories for the current value space. This tells the agent how to obtain valid inputs, though it doesn't contrast with other sibling tools beyond that.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.