Access curated news stories from NPR (National Public Radio) with focus on US news, science, and culture. Returns article headline, brief summary, direct link to NPR story, and publication metadata. Use for journalistic depth and alternative perspectives on major news events.
| Name | Required | Description | Default |
|---|---|---|---|
| max_results | No | Maximum number of stories to return (default 10, recommended for fresh content) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate read-only and open-world. Description adds context by listing returned fields (headline, summary, link, metadata) and curation aspect, enhancing behavioral understanding.
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?
Three concise sentences, front-loaded with purpose, output, and usage. 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 one optional parameter and no output schema, the description fully covers purpose, output, and usage context. No gaps.
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?
Schema coverage is 100% and the parameter 'max_results' is well-described in the schema. Description does not add further parameter details, but baseline is adequate.
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?
Clearly states the tool retrieves curated NPR news stories, specifies focus areas (US news, science, culture), and distinguishes from siblings by mentioning 'journalistic depth and alternative perspectives'.
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 a use case ('journalistic depth and alternative perspectives'), implying when to choose NPR over other news sources, but does not explicitly state when not to use it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool retrieves news from a distinct source (AP, BBC, HN, NPR, Google News) with no functional overlap, making it easy for an agent to select the correct one.
All tool names follow the consistent 'get_<source>_news' pattern in snake_case, providing a clear and predictable naming convention.
With 5 tools covering major global and niche news sources, the count is well-scoped for the server's purpose without being overwhelming or insufficient.
The set covers a broad range of news sources (global, US, UK, tech), though missing some major outlets like Reuters or an ability to fetch by category, but core retrieval is solid.