Skip to main content
Glama
Sign In

Xodia

by ai.xodia
OverviewDiscussionsAdmin

Move file

move_file

Moves or renames a file or folder.

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

Input Schema

NameRequiredDescriptionDefault
toYes
fromYes
projectIdYesProject id from list_projects

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare that this is not read-only, not destructive, and closed-world, but the description adds no further behavioral detail. It does not explain overwrite behavior, what happens when the source is missing, whether parent folders are created, or how projectId affects the move.

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?

The description is a single front-loaded sentence with no redundant wording. Its brevity is efficient, though it leaves important operational details to be inferred.

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?

For a three-parameter mutation tool with low schema coverage and no output schema, the description is too sparse. An agent still lacks essential context about destination semantics, overwrite rules, and path expectations before invoking it safely.

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

Parameters2/5

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

Only projectId has schema documentation, while from and to are undocumented with 33% overall schema coverage. The description implies a source and destination through 'moves', but it does not clarify path format, whether from and to are absolute paths, or how renaming differs from moving.

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 and resource: it moves or renames a file or folder. It is clear enough to distinguish from list/read/delete siblings, but it does not differentiate itself from closely related tools such as update_folder or move_page.

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 guidance on when to use this tool versus alternatives, nor any prerequisites such as required permissions or whether the destination must already exist. Usage is only implied by the verb 'moves'.

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

All Xodia toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources