Skip to main content
Glama

Find a website's RSS/Atom feeds (declared links and common paths like /feed and

feeds
Read-only

Find a website's RSS/Atom feeds (declared links and common paths like /feed and /rss.xml) and return the latest items from the first one: title, link, date, summary. Takes 1-5 s. Free: 20 calls/day per user across free tools, no payment needed. Above that: $0.003 per call (x402, USDC on Base).

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

Input Schema

NameRequiredDescriptionDefault
urlYesPublic http(s) URL
limitNoMax items (1-50, default 20)
paymentNox402 payment: the base64 PAYMENT-SIGNATURE value signed for the requirements returned by an unpaid call (USDC on Base, gasless). Omit on the first call to get the price and requirements.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations cover read-only and open-world traits, yet the description adds genuinely useful behavior: a 1-5 s latency expectation, the cost model (20 free calls/day per user, then $0.003 via x402 USDC on Base), and the key limitation that only the items from the FIRST discovered feed are returned. It does not state what an empty result looks like, which keeps it from a 5.

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?

Front-loaded with the purpose and return shape, followed by latency and pricing. Sentences are dense but each carries information; the pricing clause is long but functionally necessary for a paid tool.

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?

No output schema exists, and the description compensates by enumerating the returned fields and noting the single-feed scope. Missing only the no-feed-found outcome and any hint about crawling depth, minor for a 3-parameter read tool.

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?

Schema coverage is 100%, so url, limit, and payment are already documented. The description adds pricing context that informs whether payment will be required, but adds nothing about the limit parameter or URL constraints beyond the schema; baseline 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?

States a specific verb and resource (find a website's RSS/Atom feeds), the discovery methods used (declared links and common paths like /feed and /rss.xml), and the return shape (latest items from the first feed: title, link, date, summary). An agent knows exactly what comes back without opening the schema.

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

Usage Guidelines3/5

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

Usage is implied by the task (feed discovery for a public URL), but there is no explicit when-to-use guidance, no statement of what happens when no feed exists, and no routing to or away from any sibling. Adequate but with clear gaps.

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.