Skip to main content
Glama

Rename a folder

rename_folder
DestructiveIdempotent

Use this when the user wants to rename a folder. A name another folder of the same kind already has is refused. Free.

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

Input Schema

NameRequiredDescriptionDefault
nameYesThe new name.
folderIdYesThe folder's id.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the annotations, it discloses two real behavioral facts: name collisions with another folder of the same kind are refused, and the operation is "Free" (no cost/credit). It does not explain why the tool is flagged destructive (the previous name is lost) or whether the uniqueness check is case-sensitive, which would have completed the picture.

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?

Three short, front-loaded sentences with no filler; the trigger comes first. The bare fragment "Free." is efficient but slightly ambiguous about whether it means cost, credits, or rate limits.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter, non-open-world mutation with rich annotations and no output schema, the description supplies the trigger, the key failure mode (duplicate name refusal), and cost. Preexisting-name behavior on error is the only minor omission, and the annotations already carry the safety profile.

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 100% and both parameters (folderId, name) are documented in-schema with length and pattern constraints, so the schema carries the semantic load. The description adds no meaning beyond it, which is the baseline for full coverage.

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?

The description states a specific verb and resource ("rename a folder"), which is clearly distinct from sibling tools like create_folder and delete_folder without needing to name them. It stops short of explicit sibling differentiation, so it lands just under the top mark.

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?

It gives a clear triggering condition ("when the user wants to rename a folder") but offers no when-not guidance and points to no alternatives, e.g. that create_folder should be used for a genuinely new folder rather than a rename.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources