Skip to main content
Glama

Feed latest

feed_latest
Read-onlyIdempotent

Read the latest entries from any public RSS/Atom feed URL or auto-discovered website feed. $0.002 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1). Call once without payment for the terms, sign them with your own wallet, call again with payment.

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_latest"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesRSS/Atom feed URL or page URL that advertises one (http/https)
paymentNoa signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE). Pass it and the purchase completes inside this tool call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare the read-only, open-world, idempotent profile. The description adds what annotations cannot: a per-call price ($0.002), the x402 payment requirement, accepted chains/currencies (USDC on Arc/Base/Solana, XNT on X1), and the fact that supplying `payment` completes the purchase inside the same call. That is substantive operational context beyond structured fields.

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?

Three sentences, front-loaded with purpose before cost and payment mechanics, with no filler. The payment sentence is densely packed but every clause (price, protocol, currencies, two-step handshake) is load-bearing for correct invocation.

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 two-parameter, fully documented, non-destructive read tool, the definition covers purpose, cost, and the payment handshake completely. The only gap is that with no output schema it never indicates what an entry looks like (item count, fields), which an agent would need to interpret results.

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?

Schema coverage is 100%, so the baseline is 3, but the description upgrades understanding of `payment` by framing it as a signed x402 payload obtained from a prior terms call and by explaining that passing it finalizes the purchase. It adds workflow meaning the schema's one-line description does not convey.

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 first sentence names a specific verb and resource ('Read the latest entries') and scopes the input precisely ('any public RSS/Atom feed URL or auto-discovered website feed'). That is enough to tell it apart from page/web extraction siblings such as page_extract or web_read without opening either schema.

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 gives clear context for use (public feeds, or a page URL that advertises a feed) and a concrete invocation procedure: call without `payment` to obtain terms, sign, then call again with `payment`. It stops short of naming an alternative tool for cases where no feed exists, so selection guidance is contextual rather than explicit.

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