Skip to main content
Glama
rss-mcp

rss-mcp

by huangcheng

read_entry

Retrieve a single RSS or Atom entry by ID, optionally fetching full article content and updating its read status.

Instructions

Return one entry. fetch_full replaces content only when article text is returned. mark_read sets read state.

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": {
      "entry_id": "<entry_id>"
    },
    "name": "read_entry"
  }
}

Input Schema

NameRequiredDescriptionDefault
entry_idYes
mark_readNo
fetch_fullNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose two non-obvious traits: mark_read mutates read state, and fetch_full only replaces content when article text is actually returned. It omits error behavior for a missing entry_id, permission needs, and any indication that this is otherwise a read operation.

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?

Three short, front-loaded sentences with no filler. The fetch_full sentence is slightly elliptical in wording but still decodable.

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?

An output schema exists, so return values need not be described. However, with zero annotation coverage and 0% schema descriptions, the definition is thin on failure modes and on the exact semantics of fetch_full when the feed provides no article text.

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 0%, so the description must compensate, and it does explain the two non-trivial booleans (fetch_full's conditional content replacement and mark_read's side effect). entry_id is left entirely undefined, and it doesn't say what content fetch_full substitutes when no article text exists.

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?

"Return one entry" is a specific verb+resource that implicitly distinguishes this from the list/search siblings by scope (a single entry). It stops short of explicitly naming list_entries or search_entries as the alternatives for multi-entry retrieval.

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: fetch a single entry, optionally fetching full article text or marking it read. There is no explicit when-to-use guidance versus list_entries/search_entries and no guidance on when the caller should set fetch_full or mark_read.

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