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

aliyun-agent-sandbox-mcp

Rename or move a path

file_rename
Destructive

Rename or move files and directories within a sandbox by specifying the existing and new paths.

Instructions

Rename or move a file or directory inside the sandbox.

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": {
      "from": "<from>",
      "to": "<to>"
    },
    "name": "file_rename"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesNew path.
fromYesExisting path.
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

C2.9/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, so the agent knows this mutates state. The description adds only the sandbox scoping and does not disclose the destructive specifics that matter most here: whether an existing destination is overwritten, whether the source is lost on failure, or whether the rename is atomic. For a destructive move operation, that is a meaningful gap.

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, and the scope constraint is stated up front. It is efficient, though the brevity edges toward under-specification rather than optimal conciseness.

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?

With only three parameters, full schema coverage, existing annotations, and no output schema, the definition is minimally adequate. It nonetheless omits the overwrite/failure semantics that an agent needs before invoking a destructive rename, which is the main missing piece.

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%, with 'from' and 'to' clearly labeled as existing path and new path, so the baseline of 3 applies. The description adds no further meaning about path format, sandbox-relative vs absolute paths, or whether 'to' may point outside the sandbox.

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?

The description uses specific verbs plus the resource ('Rename or move a file or directory') and scopes it to the sandbox, so the agent can tell exactly what operation it performs. It does not contrast itself with any sibling, but no listed sibling plausibly overlaps with rename/move, so ambiguity is low.

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 guidance on when to use this versus alternatives, no preconditions (e.g. whether the destination must not exist, whether parent directories must already exist), and no note on cross-sandbox moves. The only usage signal is the implicit 'inside the sandbox' scope.

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