feed-reader-mcp

Fetch a feed

fetch_feed

Fetch and parse an RSS or Atom feed to retrieve recent items including titles, links, dates, and snippets.

Instructions

Fetch and parse a single RSS or Atom feed and return its recent items (title, link, date, snippet).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "<url>"
    },
    "name": "fetch_feed"
  }
}

Input Schema

Name	Required	Description	Default
`url`	Yes	The feed URL (RSS or Atom).
`limit`	No	Maximum number of items to return.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 7, 2026

TDQS

A4/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are present, so the description carries the full burden. It states the core behavior (fetch, parse, return items) and even lists fields, but does not disclose edge cases, error handling, authentication, or response format. This is adequate but minimal, offering no extra depth.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, front-loaded sentence that states the action and output without redundancy. Every element is meaningful and the length is ideal for a tool of this simplicity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple and the schema is self-explanatory. The description lists the return fields, which is helpful since there is no output schema. However, it does not mention the effect of the 'limit' parameter on the response or compare with 'fetch_many', leaving minor gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema covers both parameters fully: 'url' with format uri and 'limit' with default, minimum, and maximum. The description adds no additional parameter details, but since schema coverage is 100%, the baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool fetches and parses a single RSS or Atom feed and returns recent items with specific fields (title, link, date, snippet). The word 'single' distinguishes it from the sibling tool 'fetch_many', making the purpose explicit and non-confusable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context that this tool is for a single feed, which implies it is the right choice when one feed is needed. It does not explicitly name the alternative 'fetch_many' or provide exclusion criteria, but the 'single' qualifier gives sufficient guidance for most cases.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server