Skip to main content
Glama
julianbei

ARNO

by julianbei
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Local

arno.delete_file

Destructive

Delete a file from the active worktree; fails if the path is missing or is a directory. To edit content, use replace_text or apply instead.

Instructions

Delete a file, not a directory; fails if it does not exist. Reverting to an earlier checkpoint recreates it. To edit content use replace_text or apply.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesFile path to delete.
rootNoWorktree for this call. Default: the one set with workspace, else the start tree.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.0.17
    • changedInput schema / properties / root / description
      Previous value: -"Worktree of this repository to act in. Defaults to the session's workspace."New value: +"Worktree for this call. Default: the one set with workspace, else the start tree."
  2. Changed1 schema field changedv0.0.15
    • addedInput schema / properties / root
      Added value: +{
+  "description": "Worktree of this repository to act in. Defaults to the session's workspace.",
+  "type": "string"
+}
  3. Addedv0.0.12

TDQS

A4.3/5.0
Behavior4/5

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

Annotations declare only destructiveHint=true; the description adds genuinely new behavior: the tool errors when the path is absent, and deletion is recoverable because reverting to an earlier checkpoint recreates the file. That recoverability note is the single most decision-relevant fact for an agent about to destroy state, and it is not available anywhere else.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short clauses, front-loaded with the core action and its main constraint, then failure behavior, then the alternative-tool routing. No filler and nothing repeated from the schema or annotations.

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 destructive tool with no output schema, the description covers the essentials: what is deleted, what is not (directories), failure mode, recoverability, and where to go for the adjacent edit operation. Nothing an agent needs to invoke it correctly appears to be missing.

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% for both parameters (path, root), so the schema already carries the semantics. The description contributes only the indirect file-vs-directory constraint on 'path' and says nothing about the 'root'/worktree parameter, so 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?

States a specific verb+resource ('Delete a file') and immediately narrows the scope with 'not a directory', which an agent needs in order to avoid misusing it. It also names the sibling tools (replace_text, apply) that serve the adjacent editing intent, so it is distinguishable from them without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear conditions: only files (not directories), and it fails if the target does not exist. It routes editing intent to replace_text or apply. What it does not state is any prerequisite for deletion (e.g. permissions, whether the file must be closed/unmodified) or an alternative for removing directories.

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