Skip to main content
Glama

ToolSnap MCP

by app.toolsnap

rss_parse

Read-only

Fetch/parse an RSS or Atom feed into JSON. Saves 90%+ tokens vs raw XML.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesFeed URL.
maxItemsNoMax 200.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • addedInput schema / properties / url / description
      Added value: +"Feed URL."
  2. Changed2 schema fields changed
    • changedInput schema / properties / maxItems / description
      Previous value: -"Max feed items to return (default 20, max 200)."New value: +"Max 200."
    • removedInput schema / properties / url / description
      Removed value: -"RSS or Atom feed URL (http:// or https://)."
  3. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, and the description adds the behavioral detail that it parses both RSS and Atom formats and returns JSON, plus a token-saving benefit. It does not disclose error handling or rate limits, but the bar is lowered by the readOnlyHint annotation.

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 sentence that is concise and information-dense, with no wasted words. Every part adds value.

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?

Given the tool's simplicity (2 params, full schema coverage, readOnlyHint annotation), the description is adequate. It specifies input (RSS/Atom) and output (JSON) and adds a useful performance note. It doesn't explain return structure, but an output schema is absent and not strictly required.

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 100% (both url and maxItems have descriptions), so the baseline is 3. The tool description does not add parameter-specific meaning beyond what the schema already provides.

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?

Description clearly states the tool fetches/parses RSS or Atom feeds into JSON, using a specific verb and resource. It distinguishes from siblings like sitemap_parse and fetch_html by the feed-specific resource.

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 context is implied by the resource type (RSS/Atom feed) but the description does not explicitly state when to use this tool vs alternatives or provide exclusion criteria. The token-saving note hints at a use case but is not a direct guideline.

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

All ToolSnap MCP toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0
Disambiguation3/5

Several tools overlap in fetching and processing web content (fetch_extract, fetch_html, fetch_metadata, html_to_markdown), which could confuse an agent. However, descriptions clarify output types, so most tools are distinguishable.

Naming Consistency3/5

Names follow mixed conventions: verb_noun (fetch_html, remove_background), noun_verb (csv_query, rss_parse), and noun_noun (tool_catalog, screenshot_url). Each name is descriptive, but the lack of a consistent pattern makes it harder to guess tool names.

Tool Count4/5

With 17 tools, the count is slightly above the ideal 3-15 range but still manageable. The inclusion of 5 meta-tools (pricing, tool_catalog, task_recipes, memory_snippet, use_tool) inflates the count but serves a discovery purpose.

Completeness4/5

The toolkit covers a broad range of web and data tasks (fetch, parse, query, convert, image, SEO). Minor gaps exist (e.g., no OCR, no image editing), but use_tool can dynamically access additional tools, mitigating incompleteness.

Resources