Skip to main content
Glama

Delete one code file

delete_file
Destructive

Permanently remove a single code file from a qu4zr workspace. Preview first without confirm, then confirm to delete and see which blocks and files still import it.

Instructions

Permanently deletes ONE code file. Requires confirm=true; call without confirm first to preview. The reply lists the blocks and files that still import it — those are now broken references, which is not cascaded for you: only the author can decide what should replace them.

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": {
      "workspaceId": "<workspaceId>",
      "name": "<name>"
    },
    "name": "delete_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesCase-sensitive file name, folders with "/" — e.g. "pages/app.css", "lib/http.js".
confirmNoMust be true to delete. Omit/false returns a preview only.
workspaceIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.53.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare destructiveHint=true; the description adds the substantive behavior the annotation cannot convey: the deletion is permanent, there is a preview mode before committing, dependency breakage is reported but deliberately not cascaded, and the reply enumerates the blocks and files still importing the file. That is exactly the extra context an agent needs before an irreversible call.

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 sentences, front-loaded with the permanent-delete scope, then the confirm requirement, then the dependency caveat. No filler, and each sentence carries a distinct decision-relevant fact.

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 destructive tool with no output schema, the description covers permanence, preview, and the shape of the reply (broken references). The only omission is the meaning/scope of workspaceId, which is left undocumented in both the schema and the description; otherwise an agent has what it needs to call correctly.

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 67% and the schema already documents name (case-sensitive, slash-separated folders) and confirm (true deletes, omit/false previews). The description reinforces the confirm-then-preview workflow in the body text, which is useful but largely duplicative, and it leaves workspaceId entirely unexplained in both schema and description. A 4 reflects the reinforcement of the two-step confirm semantics beyond the raw field definitions.

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 ('Permanently deletes ONE code file') and the capitalized 'ONE' plus 'file' distinguishes it from block- or workspace-level deletion siblings. An agent can identify the operation and its granularity 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 Guidelines4/5

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

Gives an explicit invocation protocol: requires confirm=true, and call without confirm first to preview. It also sets the expectation that broken references are not handled for you. It does not name an alternative tool for replacing references (e.g. edit_file) or say when a file should be edited rather than deleted, so this is strong context but short of full alternative routing.

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