Skip to main content
Glama
rss-mcp

rss-mcp

by huangcheng

list_entries

Retrieve cached RSS/Atom entries with optional filters for subscription, date, and unread status; bodies are omitted so agents can scan and manage feeds without loading full content.

Instructions

List cached entries (bodies omitted). Limit falls back to the server default and is clamped.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
sinceNo
unread_onlyNo
subscription_idNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/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 burden. It usefully discloses that bodies are omitted and that limit defaults and is clamped, but it does not cover read-only nature, ordering, pagination, or filter behavior.

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?

Two tight sentences, front-loaded with purpose and with no filler. The size is appropriate for the amount of information conveyed.

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?

For a four-filter list tool with no annotations and no schema parameter descriptions, the definition is under-specified. The output schema reduces the need to explain return values, but filter semantics remain missing.

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%, so the description must compensate. It explains only the limit parameter's fallback and clamping behavior; since, unread_only, and subscription_id receive no semantics beyond their names.

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?

Uses a specific verb and resource ('List cached entries') and adds the scope qualifier that bodies are omitted, which helps distinguish it from read_entry. It does not explicitly differentiate itself from search_entries, so it falls short of top clarity.

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 explicit when-to-use or when-not-to-use guidance; the only signal is 'bodies omitted', which weakly implies read_entry for full bodies. With no mention of search_entries or filtering alternatives, the agent must infer tool selection.

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