list_feedsList the curated software-development feeds (id, title, category, source). Optionally filter by category (dev) 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: dev. |
Changes observed during successful MCP inspections.
Input schema / examplesAdded value: +[
+ {
+ "category": "dev"
+ },
+ {
+ "query": "javascript"
+ }
+]Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare read-only and idempotent; description adds that feeds are 'curated software-development' and lists returned fields, providing useful context 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 sentences: first states purpose and output fields, second covers optional filters and sibling pointer. 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 listing tool, description specifies output fields, filters, and sibling relationship. No output schema exists, but the description compensates adequately.
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 descriptions already cover both parameters (query and category) at 100%. Description restates their usage but adds 'dev' as an example category value, which is sufficient.
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 the tool lists curated software-development feeds with specific fields (id, title, category, source) and distinguishes from 'read_feed' by suggesting to pass an id to 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?
Provides optional filters (category 'dev' or keyword) and explicitly directs to 'read_feed' for a single feed, guiding appropriate usage.
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.