Skip to main content
Glama
freshrss-mcp

freshrss-mcp

by hrsather

freshrss_delete_category

Destructive

Deletes a specified category in FreshRSS after explicit confirmation, allowing cleanup of unused or unwanted feed groups.

Instructions

Delete a category. Requires confirm=true.

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

Input Schema

NameRequiredDescriptionDefault
nameYes
confirmNo

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 destructiveHint=true, readOnlyHint=false and idempotentHint=false, so the safety profile is covered structurally. The description adds a genuinely useful behavioral detail — that a confirm=true gate is required — but says nothing about whether contained feeds are deleted, whether the operation can be undone, or what errors arise when confirm is false.

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, front-loaded with the action and followed by the precondition, with no filler. Slightly terse for a destructive tool, but nothing wasteful.

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, and annotations cover the safety profile. Still missing is the consequence of deletion (cascade to feeds? loss of read state?), which matters for a destructive, non-idempotent tool with zero parameter documentation.

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 carries the full burden; it partly compensates by explaining the confirm flag's required value, but the mandatory `name` parameter and its expected format/lookup behavior remain entirely undocumented.

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 ("Delete a category"), which is immediately distinguishable from the rename/edit siblings. It stops short of explicitly naming alternatives, but the action itself is unambiguous.

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?

The clause "Requires confirm=true" gives an invocation precondition, which is useful, but there is no guidance on when to prefer this over options like renaming or unsubscribing, and no statement about what is affected or whether the action is reversible.

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