Skip to main content
Glama
@caelaralabs/mcp

@caelaralabs/mcp

caelara_api_rss_json_normalizer

Convert RSS or Atom feeds into structured JSON with configurable item limits for easier parsing and integration.

Instructions

[Web Intelligence] Normalize RSS/Atom feeds to JSON Measured p50 12 ms, p95 15 ms (2026-11-21, benchmarks.caelaralabs.com). Calls https://api.caelaralabs.com.

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

Input Schema

NameRequiredDescriptionDefault
urlYesFeed URL
limitNoMax items (default 50)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.2/5.0
Behavior3/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. It does reveal a meaningful behavioral trait that the agent could not otherwise know: the tool makes a network call to api.caelaralabs.com, plus measured latency figures. However, it omits auth requirements, rate limits, failure behavior for unreachable or malformed feeds, and what 'limit' does when truncated.

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 short clauses, front-loaded with the purpose, followed by performance data and the endpoint. The benchmark citation is somewhat promotional but does convey real operational context, and there is no filler prose.

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 two-parameter tool with no output schema, the description is adequate but not complete: the agent cannot tell what the returned JSON looks like (item fields, pagination, error shape). Since no output schema exists, some return-shape context would have been valuable.

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%, with both 'url' (Feed URL) and 'limit' (Max items, default 50) documented inline, so the baseline is 3. The description adds no additional semantics, such as accepted URL schemes or whether limit applies before or after normalization.

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?

States a concrete verb and resource: normalize RSS/Atom feeds into JSON. The feed-specific framing distinguishes it from generic converters like caelara_docs_xml_to_json_clean, though the description never names that sibling explicitly.

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 guidance on when to pick this over alternatives such as the XML-to-JSON or HTML-table tools, no stated prerequisites, and no exclusions. The agent must infer usage purely from the tool name and the word 'RSS/Atom'.

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