Skip to main content
Glama
Sign In
mcp-red-web-utils

mcp-red-web-utils

by hsharmanov02
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

rss

Parse syndication and Atom feeds into JSON for agent workflows; payment is per call in USDC on Base via x402.

Instructions

Parse an RSS/Atom feed into JSON (paid per call, USDC on Base via x402)

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

Input Schema

NameRequiredDescriptionDefault
urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that the call is paid per call in USDC on Base via x402, but it does not describe error behavior, rate limits, or output structure.

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?

The description is a single efficient sentence with the core purpose front-loaded and the payment detail appended. Nothing is wasted.

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

Completeness3/5

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

For a simple one-parameter tool this covers the essential input and payment model. However, without an output schema and with no annotation coverage, the description could say more about what the returned JSON contains or how failures behave.

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 description coverage is 0%, so the description must compensate. It implies the sole url parameter is the RSS/Atom feed URL, which is useful, but it adds no format or validation details beyond that.

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 states a specific verb and resource: parse an RSS/Atom feed into JSON. This is clear and actionable, though it does not distinguish the tool from potentially related siblings such as reader.

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 purpose: an agent should use this when it has an RSS/Atom feed URL and wants JSON. However, there is no explicit guidance about when not to use it or which sibling tool might be preferable.

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

Deploy Server

Other Tools