Skip to main content
Glama
rss-mcp

rss-mcp

by huangcheng

fetch_feed

Retrieve entries from one RSS or Atom subscription, or from all subscriptions when no subscription ID is given.

Instructions

Fetch one subscription, or every subscription when the id is omitted.

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

Input Schema

NameRequiredDescriptionDefault
subscription_idNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. "Fetch" implies a read-only operation and the all-vs-one behavior is disclosed, but permissions, failure behavior for an invalid id, and pagination or result size are unstated; the existing output schema covers return shape.

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?

A single sentence that front-loads the primary action and immediately qualifies the optional-parameter case. Nothing is wasted and nothing is ambiguous in phrasing.

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?

For a one-optional-parameter read tool with an output schema, the description covers the only non-obvious behavior. The remaining gap is the relationship to list_subscriptions, which matters for correct tool selection in this sibling set.

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

Parameters4/5

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

Schema coverage is 0%, so the schema only shows a nullable subscription_id defaulting to null. The description supplies the crucial semantics of that null case (return every subscription) and the integer case (return a single one), which the schema does not convey.

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?

"Fetch one subscription, or every subscription" gives a specific verb and resource plus an explicit scope rule, so the agent can tell what it returns. It does not, however, distinguish itself from the sibling list_subscriptions, which appears to cover overlapping ground.

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?

The description states the one usage-relevant condition (omit the id to fetch everything), which is genuinely useful. It offers no guidance on when to pick this over list_subscriptions, so the choice between the two must be inferred.

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