Skip to main content
Glama

remove

Deletes a file or an entire folder and its contents on a host over SSH. Specify the host and path to clean up remote files without exposing passwords or keys.

Instructions

Remove a file, or a folder with everything in it, on a host.

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": {
      "host": "<host>",
      "path": "<path>"
    },
    "name": "remove"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostYes
pathYesA path on the host; relative paths start at the home directory.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden. It does disclose the important trait that folder removal is recursive ('with everything in it'), which is real behavioral value. But it says nothing about irreversibility, whether missing paths error, or permission/authorization requirements for a destructive operation.

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?

A single front-loaded sentence with no filler; the recursive-delete consequence is stated inline. It is arguably over-compressed given what is left unsaid, but there is no wasted wording.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

A destructive filesystem tool with zero annotations and no output schema needs the description to cover safety and error behavior. Recursive deletion is mentioned, but irreversibility, permission requirements, and failure modes for nonexistent paths are all absent.

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?

Two parameters at 50% schema coverage: 'path' is documented in the schema, 'host' is not. The description adds only the notion that the operation targets a host and that the path may denote a file or a directory, which does clarify what path may point at, but no format or syntax detail beyond the schema.

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?

Specific verb (Remove) plus resource (a file, or a folder with everything in it) and the location qualifier 'on a host'. That clearly separates it from remove_host/remove_snippet/remove_tunnel, which operate on configuration entries rather than filesystem paths.

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

Usage Guidelines2/5

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

No statement of when to use this versus alternatives, no prerequisites (permissions, whether the target must exist), and no guidance on using it for a single file versus a directory tree. The only implicit usage signal is the 'on a host' scoping.

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