list_feedsList the curated international / world-news feeds (id, title, category, source). Optionally filter by category (news) or keyword. Pass an id to read_feed.
| Name | Required | Description | Default |
|---|---|---|---|
| query | No | Keyword to match in feed title/source/description. | |
| category | No | Filter by category: news. |
Changes observed during successful MCP inspections.
Input schema / examplesAdded value: +[
+ {
+ "category": "news"
+ },
+ {
+ "query": "Middle East"
+ }
+]Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, openWorldHint, idempotentHint as true, and destructiveHint false. The description adds no extra behavioral context (e.g., pagination, rate limits), but does not contradict 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, front-loaded with purpose and filtering options, 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?
Mentions returned fields and references sibling read_feed. Lacks mention of pagination or limits, but sufficient given the tool's simplicity and rich annotations.
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% with parameter descriptions already detailed. The description only rephrases 'filter by category (news) or keyword', adding no meaningful depth beyond 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?
The description clearly states 'List the curated international / world-news feeds' with specific fields (id, title, category, source). It differentiates from the sibling read_feed by suggesting using it with an id.
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 context: optionally filter by category or keyword, and directs to read_feed for an id. No explicit when-not-to-use, but sufficient for a simple list tool.
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.