Skip to main content
Glama
aliyun-agent-sandbox-mcp

aliyun-agent-sandbox-mcp

Remove a file or directory

file_remove
Destructive

Permanently deletes a specified file or directory inside an Alibaba Cloud sandbox; pass the target path and optional sandbox ID to remove it irreversibly.

Instructions

Delete a file or directory inside the sandbox. Irreversible.

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

Input Schema

NameRequiredDescriptionDefault
pathYesPath to delete.
sandbox_idNoSandbox ID, e.g. sbx-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx (returned by sandbox_create).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already supply destructiveHint=true and openWorldHint=true, so the safety profile is covered; the description's contribution is the explicit 'Irreversible' warning, which is useful confirmation. However, it says nothing about whether deleting a directory recurses, what happens if the path does not exist, or whether the operation can fail partway.

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?

Two short sentences, zero filler, with the irreversibility caveat given its own sentence so it lands with emphasis. Nothing is buried or repeated.

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

Completeness3/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 annotations covering safety and a fully documented schema, most essentials are present. The notable gap is directory semantics — recursive versus non-recursive delete — which matters greatly for an irreversible operation.

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 100%, with both 'path' and 'sandbox_id' documented in the schema including an ID format example. The description adds no meaning beyond that, so the baseline of 3 applies.

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?

States a specific verb ('Delete') and target ('a file or directory inside the sandbox'), which clearly separates it from siblings like file_rename and file_write. It never names an alternative explicitly, but the delete semantics are unambiguous.

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?

There is no when-to-use vs when-not-to-use guidance and no pointer to alternatives (e.g., file_rename to move instead of delete-and-recreate). The only scoping information is the phrase 'inside the sandbox', which restates the resource rather than guiding selection.

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