Skip to main content
Glama

Remove file

code_remove
Destructive

Remove a file, or with recursive a folder and everything in it. code_restore brings it back.

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>",
      "org": "<org>"
    },
    "name": "code_remove"
  }
}

Input Schema

NameRequiredDescriptionDefault
orgYesslug of the organization whose trees and sites to use. Required on every call, even when only one organization is listed; a path never names it.
pathYesThe address of a file or folder.
messageNoA brief note on the change.
ifChangeNoRefuse unless the tree's latest change is still this one.
recursiveNoRemove a folder and everything in it.
ifRevisionNoThe revisionId returned by code_read; refuse unless the file is still at it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the description's real contribution is that deletion is recoverable through code_restore, which materially lowers the risk calculus for an agent. It stays short of disclosing permission requirements or whether restore also covers recursively removed folders.

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?

Two tight sentences, front-loaded with the destructive action and followed immediately by the recovery path. No filler, though it could have folded the recursive condition in even more compactly.

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 destructive write with no output schema, the definition covers the scope of deletion and the reversal path, while the schema carries the full parameter detail. Nothing an agent needs in order to invoke it safely is 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%, so all six parameters including ifRevision, ifChange and message are already documented. The description only restates 'recursive' semantics, which the schema itself spells out, adding no syntax or precedence detail beyond it.

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?

A specific verb-plus-resource ('Remove a file') with the folder case called out via the 'recursive' flag, so the agent knows exactly what is deleted in each mode. It does not differentiate from the wiki removal siblings (wiki_remove, wiki_del), which is the only thing keeping it off a 5.

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

Usage Guidelines3/5

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

The mention that 'code_restore brings it back' implicitly routes the agent to the undo path, and the recursive clause tells when folder-wide deletion applies. There is no explicit when-not-to-use condition or guidance on choosing this over the sibling removal tools for wiki content.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources