Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

move_file

Move or rename files within a Godot project by specifying source and destination res:// paths, keeping project assets organized without leaving the editor.

Instructions

Move or rename a file within the project filesystem.

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>"
    },
    "name": "move_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesDestination res:// path
fromYesSource res:// path

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses almost nothing beyond 'move or rename'. It does not say whether an existing destination is overwritten, whether parent directories are created, what permissions or path constraints apply, or what happens on failure.

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?

A single front-loaded sentence with zero filler. It is efficient, though the brevity is part of the reason coverage gaps remain elsewhere.

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

Completeness3/5

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

For a simple two-parameter tool with a fully documented schema this is minimally adequate, but as an unannotated mutation tool it should clarify overwrite semantics and return behavior. No output schema exists, so the description would need to cover results if that mattered.

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% (from = source res:// path, to = destination res:// path), so the baseline is 3. The description adds only the 'within the project filesystem' scoping, not any format or edge-case detail beyond the schema.

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?

Specific verb (move/rename) and resource (a file) with scope (within the project filesystem), which helps separate it from move_node (scene-tree node) and delete_file. It does not explicitly name siblings, but the resource is clear enough for an agent to select it.

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?

No when-to-use or when-not-to-use guidance and no alternatives referenced. An agent must infer that this is the filesystem counterpart to move_node/rename operations rather than being told so.

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

Deploy Server

Other Tools