Skip to main content
Glama
freshrss-mcp

freshrss-mcp

by hrsather

freshrss_mark_read

Idempotent

Marks specified FreshRSS articles as read by ID, up to 100, to bulk-clear unread items.

Instructions

Mark articles read by id (at most 100).

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": {
      "ids": "<ids>"
    },
    "name": "freshrss_mark_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYes

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?

Annotations already declare idempotentHint=true, destructiveHint=false, and readOnlyHint=false, so the safety profile is covered. The description contributes one genuine behavioral detail beyond that – the hard cap of 100 ids – but says nothing about what happens when the cap is exceeded or how invalid ids are handled.

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?

A single front-loaded sentence with no filler, and the limit is placed where it is needed. It is a fragment rather than a full sentence, but nothing is wasted.

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?

For a one-parameter mutation tool with rich annotations and an output schema, the essentials are present: what it does, the id basis, and the 100-item bound. Gaps remain around error/overflow behavior and id format, which matter for correct invocation of a write tool.

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?

With schema description coverage at 0%, the description must carry parameter meaning, and it partially does: it identifies the array entries as article ids and adds a maximum length of 100 the schema does not express. It still omits the id format (numeric string vs. opaque token) and required/optional semantics beyond what the schema states.

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 articles read') qualified by 'by id', which distinguishes it from the sibling bulk operation freshrss_mark_all_read and from freshrss_mark_unread. It does not explicitly name those alternatives, but the scoping phrase does the disambiguating work.

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: 'by id' signals this is the targeted, per-article path rather than a bulk operation, but the description never states when to prefer it over freshrss_mark_all_read or what prerequisites exist (e.g., that the ids must be existing article ids).

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