Skip to main content
Glama
rss-mcp

rss-mcp

by huangcheng

mark_entry

Mark RSS or Atom entries as read or unread by ID to track reading state; unknown IDs are skipped.

Instructions

Mark entries read or unread. Unknown ids are skipped.

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_ids": "<entry_ids>",
      "read": "<read>"
    },
    "name": "mark_entry"
  }
}

Input Schema

NameRequiredDescriptionDefault
readYes
entry_idsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/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. It does disclose one genuinely useful trait — unknown ids are silently skipped rather than raising an error — which tells the agent the call is tolerant/idempotent. However, it says nothing about permissions required, whether the change is persisted or reversible, or what happens with an empty entry_ids array.

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?

Two short sentences with the action front-loaded and the edge-case behavior second; nothing is wasted. The only slight weakness is that both facts are compressed into terse fragments with no explicit mapping to the parameter names.

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 two-parameter boolean mutation with an output schema available for return values, the description covers purpose, parameter meaning, and out-of-range id handling — enough to invoke correctly. The remaining gap is authorization/prerequisite context, which is minor at this complexity level.

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

Parameters5/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: 'read or unread' defines the direction of the 'read' boolean, and 'Unknown ids are skipped' defines how invalid members of 'entry_ids' are handled. That covers the meaningful semantics of both required parameters, which is what the schema leaves unexplained.

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?

States a specific verb and resource ('Mark entries read or unread') and adds the state-toggling scope, so an agent can distinguish it from fetching siblings like read_entry or list_entries. It stops short of naming any sibling explicitly, so it is clear but not fully differentiated.

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 when-to-use guidance: nothing says whether this is safe to call on already-read entries, how it relates to read_entry (which presumably fetches content), or whether it should be paired with list_entries/search_entries to obtain ids. The only conditional statement concerns unknown ids, which is behavior rather than usage selection.

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