list_feedsList the curated climate & energy feeds (id, title, category, source). Optionally filter by category (climate, energy) 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: climate, energy. |
Changes observed during successful MCP inspections.
Input schema / examplesAdded value: +[
+ {
+ "category": "climate"
+ },
+ {
+ "query": "renewable energy"
+ }
+]Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly, openWorld, idempotent, non-destructive. Description adds listing scope and fields but no new behavioral traits.
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, front-loaded with purpose and fields, efficient and no filler.
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?
Complete for a simple filtered list tool with 2 optional params, no output schema; links to sibling for next action.
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 100%; description restates parameter options (category values, keyword) without adding new meaning beyond 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 'list the curated climate & energy feeds' with specific fields returned. Distinguishes from sibling read_feed by instructing to pass an id for that tool.
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?
Explains optional filters and directs to read_feed for single feed access. Lacks explicit when-not-to-use or alternatives.
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.