Skip to main content
Glama
freshrss-mcp

freshrss-mcp

by hrsather

freshrss_mark_all_read

Destructive

Marks every article in a selected stream—all, starred, feed, or category—as read, with confirmation required to prevent accidental bulk updates.

Instructions

Mark every article in a stream (all, starred, feed or category; target as in freshrss_list_articles) as read. Requires confirm=true.

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

Input Schema

NameRequiredDescriptionDefault
streamNoall
targetNo
confirmNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is known. The description adds genuinely new behavioral context by naming the confirm=true gate, which the annotations do not express. It leaves one gap: it doesn't state whether omitting confirm causes an error or a silent no-op.

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 dense sentences with the destructive scope and the confirm requirement both front-loaded; nothing is padding. The inline parenthetical listing stream modes is slightly cluttered but does real work.

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?

An output schema exists, so return values need not be described, and annotations cover destructiveness. What remains — the confirm-failure behavior and the exact target/stream pairing — is partially addressed via the sibling reference, leaving only a small completeness gap for a bulk-mutation 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?

Schema description coverage is 0%, so the description must carry the parameter burden. It partially does — stream modes are enumerated and confirm is explained — but the stream/target relationship is compressed into a parenthetical that requires opening freshrss_list_articles to fully resolve. Two of three parameters remain only thinly characterized.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Mark ... as read') and a precise scope ('every article in a stream'), which cleanly separates it from the single-article sibling freshrss_mark_read. The enumerated stream modes (all, starred, feed, category) further pin down exactly what resource is affected.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear operating context: the valid stream modes, a pointer to freshrss_list_articles for resolving `target`, and the hard requirement of confirm=true. It does not explicitly say when to prefer this over freshrss_mark_read or what happens if confirm is left false, so it falls short of full when/when-not guidance.

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