Skip to main content
Glama

Move file

code_move
Destructive

Move or rename a file, or a folder and everything in it, within its tree. Returns the tree's problems after it, such as imports the move broke.

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": {
      "from": "<from>",
      "to": "<to>",
      "org": "<org>"
    },
    "name": "code_move"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesThe address it should have, in the same tree.
orgYesslug of the organization whose trees and sites to use. Required on every call, even when only one organization is listed; a path never names it.
fromYesThe address now.
messageNoA brief note on the change.
ifRevisionNoThe revisionId returned by code_read; refuse unless the file is still at it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered structurally. The description adds real value by disclosing that folder moves are recursive and that the call reports tree-wide fallout such as broken imports, but it says nothing about overwriting an existing destination, permission requirements, or whether the move is reversible.

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?

Two tight sentences with the core action front-loaded and the consequence note second; nothing is padding. The second sentence is slightly awkwardly phrased ('Returns the tree's problems after it'), which costs a point on clarity.

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?

With no output schema, the description usefully explains what comes back (post-move tree problems, e.g. broken imports) and covers the recursive folder case. For a destructive mutation it could still say more about overwrite and permission 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 100%, so from/to/org/ifRevision/message are already documented in the schema. The phrase 'within its tree' reinforces the same-tree constraint on 'to' but the description adds no syntax or semantics beyond that.

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?

Names a specific verb pair (move/rename) and the resource, including the recursive case ('a folder and everything in it'), plus the scoping constraint 'within its tree'. It stops short of distinguishing itself from code_edit or wiki_move, so an agent still has to infer that this is the rename/move path rather than a content edit.

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 explicit when-to-use statement, no mention of when to prefer code_edit or wiki_move, and no explanation of when the optional ifRevision guard should be supplied. Usage is only implied by the verb 'move or 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