Retrieve latest news stories from BBC News covering global, regional, and domestic stories. Returns headline, synopsis, article URL, publish date, and section (world/uk/business/tech). Use for UK perspective on international news or UK-focused stories. Includes categories for targeted browsing.
| Name | Required | Description | Default |
|---|---|---|---|
| max_results | No | Number of articles to retrieve (default 10, higher values may include older stories) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate readOnlyHint and openWorldHint. Description adds details on return fields (headline, synopsis, URL, date, section) and notes that higher max_results may include older stories, which is useful behavioral info beyond annotations.
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 concise sentences that front-load the main action, then provide return details and usage guidance. No wasted words, every sentence adds 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?
Given the low complexity (one optional parameter, no output schema), the description fully covers what the tool does, what it returns, and when to use it. No gaps for the agent.
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 covers the single parameter with a description (100% coverage). Description adds value by noting that higher max_results may include older stories, which is not in the schema.
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 it retrieves latest BBC News stories with coverage of global/regional/domestic stories. Differentiates from siblings by emphasizing UK perspective and UK-focused content, distinct from AP, NPR, Hacker News, and Google News.
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?
Explicitly states when to use ('Use for UK perspective on international news or UK-focused stories'), providing clear context. Does not include explicit exclusions or alternative comparisons, but the context is sufficient.
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.