Skip to main content
Glama
freshrss-mcp

freshrss-mcp

by hrsather

freshrss_rename_category

Rename a FreshRSS category by providing its current name and the new name to reorganize feeds and keep category labels current.

Instructions

Rename a category.

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>",
      "new_name": "<new_name>"
    },
    "name": "freshrss_rename_category"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
new_nameYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.1/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=false, so safety profile is covered. The description adds nothing beyond them: it doesn't say what happens if the category doesn't exist, whether the old name is required to identify the category, or whether renaming affects feed associations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single short sentence is front-loaded and free of padding, but its brevity reflects under-specification rather than efficiency. There is no structure to speak of because there is essentially no content.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/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 explained, but a two-parameter mutation tool with zero schema coverage needs the description to disambiguate parameter meaning and failure behavior, and it does neither. The definition is not sufficient for an agent to call it confidently without guessing.

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

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the schema only supplies bare titles "Name" and "New Name". The description does not clarify whether "name" is the current category name, an ID, or a display name, nor any format or length constraints, so it fails to compensate for the coverage gap.

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

Purpose2/5

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

"Rename a category" merely restates the tool name (freshrss_rename_category) in verb+resource form, adding no distinguishing detail. It doesn't say what a category is, whether it is user-created or feed-derived, or how rename differs from sibling operations like freshrss_edit_feed.

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?

The description contains no when-to-use guidance, no prerequisites, and no mention of alternatives. Nothing tells the agent to prefer this over freshrss_delete_category or freshrss_list_categories when reorganizing categories.

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