MyClaw Toolkit MCP Server

rss_feed

Retrieve and parse RSS feed items from any URL to stay informed on new content and updates.

Instructions

Fetch and parse RSS feeds from any URL

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

Input Schema

Name	Required	Description	Default
`url`	Yes	RSS feed URL to fetch
`count`	No	Number of items

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.1Jun 23, 2026

TDQS

B3.2/5.0

Behavior2/5

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

With no annotations, the description carries full burden for behavioral traits. It mentions 'fetch' but does not disclose network dependency, timeouts, error handling, caching, or what 'parse' entails regarding output. The brevity obscures important side effects for an agent invoking a network tool.

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?

The description is a single sentence, front-loaded with the verb and resource. It is concise with no wasted words, though it could benefit from minimal additional context without sacrificing brevity.

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?

Given the simple two-parameter tool and complete schema descriptions, the description is adequate but lacks completeness regarding return format, error conditions, and network behavior. For a tool making external calls, more context is warranted.

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%, so baseline is 3. The description adds no additional meaning beyond the schema; it does not explain that 'count' limits number of items or that 'url' must be an RSS feed. The description is neutral here.

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?

The description clearly states the tool fetches and parses RSS feeds from any URL, using specific verbs and resource. It distinguishes well from siblings like web_search, news_search, and read_page, which involve different types of content or actions.

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?

The description provides no guidance on when to use this tool versus alternatives such as web_search or news_search. It lacks explicit context or exclusions, leaving the agent to infer usage from the tool name alone.

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