Skip to main content
Glama

File operations

file_ops
Destructive

Copy, move, rename, delete files or folders and create directories without a shell; deletions and overwrites stay restorable from ZeroIDE history.

Instructions

Copy, move/rename or delete files and folders, or create a folder, without a shell. delete never destroys data: the files move to ZeroIDE history and the owner can restore them in Settings → Changes. Anything replaced with overwrite=true keeps its previous version too. Prefer this to Remove-Item/Move-Item in run_command: it is reversible and the owner sees exactly what changes.

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": {
      "op": "<op>",
      "path": "<path>"
    },
    "name": "file_ops"
  }
}

Input Schema

NameRequiredDescriptionDefault
opYes
toNoDestination for copy and move.
noteNoShort human-readable explanation (1 line, in the user's language) of what you are about to do and why. Shown to the user on the approval card. Always provide when calling mutating tools.
pathYesSource (copy/move/delete) or the folder to create (mkdir). Absolute or relative to the project dir.
agentNoShort consistent identifier or display name of this agent (e.g. 'Claude · Лендинг', 'Тесты', 'Мой агент'). Used to separate tasks and route tray messages when multiple agents work in parallel.
overwriteNocopy/move: replace an existing destination file; its previous version is kept in history. Default false.
recursiveNoRequired to copy or delete a folder with its contents.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true, but the description adds the crucial nuance that deletes go to ZeroIDE history and are restorable via Settings → Changes, and that overwrite=true preserves the replaced version. That is real behavioral context beyond the structured fields and directly shapes how cautiously an agent should behave.

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?

Three sentences, front-loaded with the capability list before the safety and alternative guidance. Slight redundancy: reversibility is restated across the history sentence, the overwrite sentence, and "it is reversible," which could be tightened to one statement.

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?

For a 7-parameter mutating tool with no output schema, the description covers the operations, the recovery model, and the sibling tradeoff well. It is thin on what a call returns (e.g., resulting paths or an operation id) and never mentions the note/agent fields the schema says to always populate for mutating calls.

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 coverage is 86%, so op/path/to/note/agent/overwrite/recursive are already documented in the schema, including the history behavior of overwrite. The description's mention of overwrite=true and folders with contents adds marginal meaning over what the schema already states, so the baseline 3 applies.

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?

"Copy, move/rename or delete files and folders, or create a folder, without a shell" names concrete verbs and the resource, and "without a shell" immediately separates it from run_command. An agent can tell what this does and what it does not do without opening the schema.

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?

It names the alternative explicitly ("Prefer this to Remove-Item/Move-Item in run_command") and gives the reason (reversible, owner sees the changes), which is exactly the when-to-use signal an agent needs. The negative case (don't shell out) is stated, not implied.

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