Skip to main content
Glama

net-web-media

rss_atom_feed_validate

Validate RSS 2.0 or Atom XML syndication feeds for required channel/feed elements, entry count, pubDate/updated dates, and links.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "rss_atom_feed_validate"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNo
filePathNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/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 behavioral burden. It does disclose the concrete checks performed, which is real value, but says nothing about what a result looks like (pass/fail, error list, severity), whether validation is strict, or how failures are reported.

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?

One front-loaded sentence with no filler; the validated aspects are listed compactly. Slightly dense as a comma run-on, but every clause earns its place.

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

Completeness2/5

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

With no annotations, no output schema, and two entirely undocumented parameters, the definition leaves the agent without the two things it most needs: how to supply input and what the result contains. For a validation tool whose whole value is its verdict, that is a significant shortfall.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for both parameters, so the description must compensate and does not. It never explains the distinction between 'text' (inline feed content) and 'filePath', nor that both are optional and presumably mutually exclusive, leaving the agent to guess which to supply.

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?

Specific verb ('Validate') plus specific resource ('RSS 2.0 or Atom XML syndication feeds') and an enumeration of what is checked (required channel/feed elements, entry count, pubDate/updated dates, links). The feed-format scoping clearly separates it from siblings like sitemap_xml_validate and json_ld_schema_validate without needing to name them.

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 only implied by the resource type: an agent can infer 'use this on an RSS/Atom feed' but gets no explicit when-not guidance, no mention of alternatives, and no prerequisites. Nothing misleading, but nothing that actively routes the agent.

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