Skip to main content
Glama

apex-dev

Rss to json

rss_to_json
Read-onlyIdempotent

Parse any public RSS 2.0, Atom 1.0, or JSON Feed URL into clean structured JSON items with ISO timestamps, authors, categories, and plain-text summaries. $0.001 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1). Call once without payment for terms, then 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": "rss_to_json"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPublic http(s) URL of an RSS, Atom, or JSON Feed.
limitNoOptional max items to return (1-50, default 20).
paymentNosigned x402 payment payload (PAYMENT-SIGNATURE).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/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 safety is covered. The description adds behavior the annotations cannot: a concrete price ($0.001 per call), the accepted payment rails (USDC on Arc/Base/Solana, XNT on X1), and the two-call payment handshake. It stops short of describing failure modes (malformed feeds, non-feed URLs) or rate limits.

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?

Two sentences, front-loaded with the capability and followed by the commercial/payment constraint. Every clause carries information an agent needs — feed formats, output fields, price, payment rails, call sequence — with no filler or repetition of the title.

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?

With no output schema, the description takes on the burden of describing returns and does so (ISO timestamps, authors, categories, plain-text summaries), and it fully covers the non-obvious paid-access mechanics. Gaps are minor: no mention of error behavior for invalid or paywalled feeds, and no note on item ordering.

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 earns extra by explaining what the `payment` parameter is for and why the tool is called twice (first without payment to obtain terms). It adds no new detail on `url` or `limit` beyond the schema, which already states the 1-50 range and default 20.

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?

Uses a specific verb ('Parse') with a precisely enumerated resource ('public RSS 2.0, Atom 1.0, or JSON Feed URL') and states the output shape (structured JSON items with ISO timestamps, authors, categories, plain-text summaries). It does not name a sibling such as feed_latest or page_extract to sharpen the boundary, so it lands just short of a 5.

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?

The description gives a concrete procedural flow for the x402 paywall ('call once without `payment` for terms, then call again with `payment`'), which is genuinely useful invocation guidance. It never says when to prefer this over alternatives like feed_latest, nor any when-not conditions (e.g. private/authenticated feeds), so usage context is implied 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