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 declare readOnlyHint=true and openWorldHint=true, so the agent knows it's a safe read operation. The description adds return payload details (headline, summary, link, metadata) but doesn't disclose behavioral traits like rate limits, pagination, or ordering. With annotations lowering the bar, a mid score is appropriate.
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 well-structured sentences: purpose, return values, and usage guidance. No fluff or redundancy; every sentence contributes value.
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 read-only tool with one parameter and no output schema, the description adequately covers what it returns and when to use it. It could mention edge cases (e.g., empty results) but is sufficiently complete given the low complexity.
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 has 100% description coverage for the single parameter (max_results), including default and purpose. The description adds no additional parameter-specific meaning, so it meets the baseline but doesn't exceed it.
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 clearly states a specific verb+resource: 'Access curated news stories from NPR' with focus on US news, science, and culture. It distinguishes from sibling tools like get_ap_news and get_bbc_news by naming NPR and its niche.
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?
It provides clear context: 'Use for journalistic depth and alternative perspectives on major news events.' This implies when to select NPR over other sources, but it doesn't explicitly exclude alternatives or name sibling tools, so it's not a full 5.
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 targets a distinct news source or search functionality. The four get_* tools are differentiated by provider, and search_google_news complements them with cross-source search, eliminating ambiguity.
All tool names follow a clear verb_source pattern: get_ or search_ followed by the source identifier. This consistent convention makes the tool's function predictable from its name alone.
With five tools covering four major news providers plus a global search, the count is well-scoped for a news fetching server. Neither too sparse nor overwhelming.
The surface covers both source-specific top stories and keyword-based cross-source search, meeting the core needs of news retrieval. No critical gaps are apparent for the stated purpose.