Skip to main content
Glama

rss-latest

Returns the latest items from a public RSS 2.0 or Atom feed as JSON: title, link, published date, summary (500 chars max) and guid for each item, plus feed title and link. Inputs: ?url= (public http/https feed URL, required), ?limit= (1-50, default 10). Caps: 3 MB feed read, 50 items max, 15 s per call. Private and local addresses are refused. Feeds that are HTML pages, PDFs or binary files return ok:false with a plain reason. Free: 3 calls a day per visitor; after that $0.01 per call via x402 at https://tools.orchardshop.xyz/t/rss-latest.

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>",
      "limit": "<limit>"
    },
    "name": "rss-latest"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYese.g. https://hnrss.org/frontpage
limitYese.g. 2

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / url / description
      Previous value: -"e.g. https://hnrss.org/newest"New value: +"e.g. https://hnrss.org/frontpage"
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full burden and does so well: it names concrete caps (3 MB read, 50 items, 15 s per call), the SSRF-style refusal of private/local addresses, the ok:false failure contract for non-feed payloads, and the rate-limit/payment model (3 free calls/day, then $0.01 via x402). These are exactly the operational traits an agent cannot infer from schema alone.

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?

Payload, inputs, caps, failure modes, and pricing are ordered by what an agent needs first, and the whole thing is one dense paragraph with no filler. Every clause carries a fact (bounds, refusals, cost) rather than restating the name.

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

Completeness5/5

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

There is no output schema, so the description compensates by enumerating returned fields (title, link, published, 500-char summary, guid, feed title/link). Combined with the caps and refusal rules, an agent has everything needed to call this correctly and interpret a failure.

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

Parameters4/5

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

The description adds real meaning beyond the thin schema: url must be a public http/https feed URL, limit ranges 1-50 with a default of 10. It does not reconcile the mismatch that the schema marks limit as a required string with no default, leaving an agent to guess whether omitting limit is legal — a small but real gap given the 100% but low-value schema coverage.

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?

"Returns the latest items from a public RSS 2.0 or Atom feed as JSON" gives a specific verb (returns), a specific resource (RSS 2.0/Atom feed items), and enumerates the exact return fields. No sibling in the list does feed parsing, so no disambiguation is needed and none is missing.

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 sets clear preconditions (public http/https feed only, private/local refused) and describes failure cases (HTML pages, PDFs, binaries return ok:false with a reason). It doesn't state explicit when-not-to-use or name alternatives, but the sibling set contains no overlapping feed tool, so the omission is low-cost.

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