Skip to main content
Glama

Rename folder

mailbox_rename
Idempotent

Changes a custom folder's name; its ID and messages stay the same.

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

Input Schema

NameRequiredDescriptionDefault
idYesFolder ID from mailbox_list.
nameYesNew folder name; cannot be empty.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / id / description
      Added value: +"Folder ID from mailbox_list."
    • addedInput schema / properties / name / description
      Added value: +"New folder name; cannot be empty."
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly=false, idempotent=true, destructive=false. The description adds meaningful context beyond them: the folder ID and its contained messages are preserved, so the agent knows this is a rename, not a move or recreate. It doesn't cover permission requirements or duplicate-name handling, keeping it below a 5.

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

Conciseness5/5

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

A single tight sentence that front-loads the action and then the key side-effect guarantee. Every clause carries information; nothing is redundant.

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?

For a two-parameter rename with full schema coverage and clear annotations, the definition supplies what an agent needs: scope (custom folders), effect (ID and messages unchanged), and mutation semantics. Minor gaps remain around name-collision behavior and required permissions, but nothing essential is absent.

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 coverage is 100%, with 'Folder ID from mailbox_list' and 'cannot be empty' already documented in the schema. The description adds essentially no parameter-level detail beyond what the schema states, so the baseline 3 applies.

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 names a specific verb ('Changes a custom folder's name') and resource ('custom folder'), separating it from mailbox_create/mailbox_delete/mailbox_list. It doesn't explicitly name a sibling to route against, but the resource plus the 'custom' qualifier makes the operation identifiable without opening the schema.

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?

There is no explicit when-to-use or when-not-to-use statement and no mention of alternatives. The qualifier 'custom folder' implies that system folders are out of scope, which is useful implied guidance, but the agent must infer it.

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.