Skip to main content
Glama

Manawa Terminal

Rename library folder

rename_library_folder

Rename a library folder.

Args:
    folder_id: The folder UUID
    name: New folder name

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

Input Schema

NameRequiredDescriptionDefault
nameYes
folder_idYes
strategy_idNoStrategy this call belongs to. UUID from list_strategies. The card this call writes keeps that id. Omit when the call is not part of a strategy.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / strategy_id
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Strategy this call belongs to. UUID from list_strategies. The card this call writes keeps that id. Omit when the call is not part of a strategy.",
      +  "title": "Strategy Id"
      +}
  2. First observed

TDQS

C2.8/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 openWorldHint=false, so the description should add context beyond that. Instead it says nothing about permission requirements, whether the name must be unique within a parent, whether the rename is reversible, or what happens on conflict. The description contributes no behavioral detail beyond what annotations provide.

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 one-line description is front-loaded and efficient, but the subsequent Args block duplicates schema information rather than adding meaning. This is not wastefully long, but it could be collapsed into the introductory sentence without any loss.

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?

This is a mutation tool, and the absence of prerequisites, permission notes, or conflict behavior leaves meaningful gaps for an agent invoking a rename operation. Although an output schema exists and return values do not need to be explained, the description fails to clarify the optional strategy_id parameter or any mutation-specific behavior.

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 33%, since only the optional strategy_id parameter has a description in the schema. The description clarifes that folder_id is 'The folder UUID' and name is the 'New folder name', which maps to two of the three parameters, but it omits explanation of the optional strategy_id parameter that the schema documents separately. At 33% coverage, the description compensates for only part of the gap.

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+resource: 'Rename a library folder.' This is unambiguous and separates it from sibling tools like move_library_folder, delete_library_folder, or create_library_folder. It stops short of explicitly naming those alternatives, but the verb itself is distinctive.

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?

There is no guidance on when to use this tool versus alternatives, no mention of prerequisites, and no note on how it differs from move_library_folder. The description only declares what the tool does, leaving the agent to infer the usage context.

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