Skip to main content
Glama
PhononX

Carbon Voice

by PhononX

move_folder

Destructive

Relocate a folder to a new parent folder or to the workspace root. Pass a folder_id for a new parent or workspace_id for the root.

Instructions

Move a folder into another folder, or up to a workspace root. USE WHEN: Relocating a folder. Pass folder_id for a new parent folder, or workspace_id to move it to the workspace root — one or the other, not both. USE INSTEAD: update_folder_name to rename in place. move_message_to_folder for a single message rather than a folder. FIRST: id comes from get_root_folders (field results[].id) — call it first if you don't have one. EXAMPLE: {"id":"folder-abc","folder_id":"folder-parent"} RETURNS: The moved folder, same shape as get_folder. ERROR BAD_REQUEST: Both folder_id and workspace_id were given, or neither, or the move would nest a folder inside itself. — Pass exactly one destination.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
folder_idNoFolder ID
workspace_idNoWorkspace ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the mutation risk is known. The description adds valuable behavioral context: the exclusivity constraint (one destination, not both), the self-nesting error condition, and the return shape. It doesn't detail side effects on child folders, but the provided context is strong.

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?

The description is compact, front-loaded with the core action, and every section earns its place: use-when, alternatives, prerequisite, example, and error handling. No filler or repetition.

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 3-parameter mutation tool with no output schema, the description covers the key decision (which destination parameter), the prerequisite call, the error case, and the return shape. An agent has enough to invoke it correctly without additional lookups.

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

Parameters4/5

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

Schema coverage is 67%, and the description compensates by explaining the semantic difference between `folder_id` and `workspace_id`, including the 'one or the other, not both' rule. It also clarifies where `id` comes from. This adds meaning beyond the bare schema descriptions.

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

Purpose5/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 ('Move a folder into another folder, or up to a workspace root') and clearly distinguishes it from siblings like `update_folder_name` and `move_message_to_folder`. The purpose is unambiguous and immediately actionable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The 'USE WHEN' section explicitly states when to use the tool, and 'USE INSTEAD' names alternatives with conditions. It also provides a 'FIRST' prerequisite and an example, giving an agent complete routing and sequencing guidance.

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