Skip to main content
Glama

Caelara Labs Web Intelligence

rss_json_normalizer

Normalize RSS/Atom feeds to JSON

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

Input Schema

NameRequiredDescriptionDefault
urlYesFeed URL
limitNoMax items (default 50)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden, and it says nothing about network fetching, redirects, failure behavior on non-feed URLs, or how limit truncation is applied. The one behavioral fact it does convey — that the output is JSON — is minimal for a fetch-and-transform tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

At six words there is zero filler and the core action is front-loaded. The brevity crosses from concise into under-specified, so it does not earn top marks for structure.

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?

The parameters are fully documented in the schema and the description names the output format, so the essentials are covered. With no annotations and no output schema, though, the agent gets no warning about invalid-feed errors or fetch side effects, leaving real gaps for a network-touching 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%: url is documented as 'Feed URL' and limit as 'Max items (default 50)', so the schema does the work. The description adds no meaning beyond that, and per the coverage rule a baseline 3 applies.

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 — converting RSS/Atom feeds into JSON — so an agent knows exactly what the tool does. It stops short of distinguishing itself from URL-fetching siblings like url_to_markdown or sitemap_crawler, which also take a URL, so the boundary is not drawn.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance. The only implied rule is 'use this for feeds,' and nothing tells the agent what to do with a URL that is not a feed, or which sibling to pick when the target might be an HTML page instead.

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