Skip to main content
Glama

move_file

Move a saved file to another folder, creating it if needed while preserving the file name, extension, and description; canvas-linked files are refused.

Instructions

File an item into a different folder. This is the other half of describe_item: describing makes a pile findable, filing makes it tidy, and both are the slow work somebody drops things into Inbox to avoid doing by hand.

Use list_folders first to see what folders exist. The folder is created if it does not exist yet.

REFUSES for a file that is on a canvas, and the reason is worth knowing rather than working around: canvas elements store the path of the file they show, those elements live inside the app, and only the app can rewrite them. Studiolo's own move updates every canvas as it goes. A move made from out here would leave those canvases pointing at nothing, with no way for either side to notice. Move it in Studiolo instead.

REFUSES ALSO when it cannot find out whether the file is on a canvas. Missing information is not permission.

The filename and its extension are unchanged — use rename_file for the name. Nothing is overwritten: a collision gets a numbered suffix. Any description the file has travels with it.

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

Input Schema

NameRequiredDescriptionDefault
pathYesThe item, as search_inspo reports it.
folderYesFolder within the root, e.g. 'packaging' or 'type/specimens'. Use '.' for the root itself.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does so well: it discloses auto-creation of the folder, non-overwrite with numbered suffix, preservation of the description, unchanged filename, and two refusal cases including the fail-closed rule when canvas status is unknown. The only gap is that it doesn't describe the return value, though no output schema exists.

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 critical constraints are front-loaded, but the opening metaphor about Inbox and 'the slow work somebody drops things into Inbox to avoid doing by hand' is padding that doesn't help an agent decide or invoke. The refusal rationale is useful but wordier than needed.

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 two-parameter mutation tool with no annotations and no output schema, the description covers side effects, refusals, collision behavior, and alternatives — everything an agent needs to call it correctly or route elsewhere.

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 100%, so the baseline is 3, but the description adds real meaning beyond the schema by stating the folder is created if it does not exist and that the path is unchanged by the move.

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?

States a specific verb and resource ('File an item into a different folder') and explicitly contrasts with rename_file for name changes, so an agent can distinguish it from siblings without opening schemas.

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?

Gives explicit prerequisites ('Use list_folders first'), names the alternative for renaming, and states two refusal conditions with the recommended workaround (move it in Studiolo instead). When-to-use and when-not-to-use are both covered.

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