Skip to main content
Glama

Sitesy Website Intelligence

Read a feed

feed_reader
Read-onlyIdempotent

An RSS, Atom, or RDF feed normalised into dated items with summaries. Costs 0.005 USDC per call. The caller pays per call in USDC on Base through x402: the first call returns the payment requirements, and an x402 aware MCP client signs and retries automatically.

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": "feed_reader"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesA feed address, for example https://example.com/feed.xml

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the description earns credit for adding information the annotations cannot convey: a per-call price of 0.005 USDC on Base via x402, and the two-step handshake where the first call returns payment requirements and a retrying client signs automatically. It stops short of describing failure behavior, such as what happens on payment rejection or when the URL is not a valid feed.

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

Conciseness4/5

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

Two sentences, no filler. The output shape is stated first and the cost/payment model second, which is the right order for an agent deciding whether to call. The opening is a noun phrase rather than a verb phrase, a minor structural weakness.

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?

For a one-parameter, no-output-schema tool this is close to sufficient: it describes the returned item structure and the paid-call protocol that would otherwise surprise an agent. Missing edge-case behavior (invalid or non-feed URLs, payment failure) keeps it below a 5.

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?

There is a single parameter with 100% schema description coverage, including a concrete example URL and a maxLength constraint, so the schema already carries the semantics. The description adds nothing about the url parameter itself (acceptable feed schemes, redirects, auth-protected feeds), so baseline 3 applies.

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

Purpose4/5

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

The description names the resource precisely (an RSS, Atom, or RDF feed) and states what is returned (dated items with summaries), which clearly separates it from sibling tools like page_reader that handle HTML pages. It never uses an explicit verb such as 'fetches' or 'reads the feed at url', leaving the action implied by the name and title rather than stated.

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

Usage Guidelines2/5

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

There is no guidance on when to choose this over page_reader or site_check, and no statement of prerequisites or exclusions (for example, what to do with an HTML page URL). The payment flow is described, but that is invocation mechanics, not tool selection guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources