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

aliyun-agent-sandbox-mcp

Extend the sandbox TTL

sandbox_set_timeout

Update a running sandbox's time-to-live so long-running jobs are not reaped before completion.

Instructions

Update the time-to-live of a running sandbox so long jobs are not reaped while they run.

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": {
      "sandbox_id": "<sandbox_id>",
      "timeout_ms": "<timeout_ms>"
    },
    "name": "sandbox_set_timeout"
  }
}

Input Schema

NameRequiredDescriptionDefault
sandbox_idYesSandbox ID, e.g. sbx-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx (returned by sandbox_create).
timeout_msYesNew TTL in milliseconds.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare destructiveHint=false and openWorldHint=true, so the description's marginal duty is small. It usefully signals the sandbox must be running, but omits whether the value replaces or adds to the existing TTL, whether it can be shortened, and any upper bound beyond the schema's JS-safe-integer maximum.

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?

A single front-loaded sentence that states the action and its rationale with no filler or redundancy.

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 two-parameter tool with full schema coverage, annotations, and no output schema, the definition covers purpose and motivation adequately. The only meaningful gap is the replace-vs-extend semantics of the timeout value.

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%, so both parameters are already documented, including the sbx- ID format and millisecond units. The description adds no clarification of the key ambiguity: whether timeout_ms is an absolute new TTL or an extension of remaining time (the title says 'Extend', the description says 'Update').

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 and resource ('Update the time-to-live of a running sandbox') plus the motivating outcome (long jobs not reaped). An agent can distinguish this from sandbox_create or sandbox_kill, though no sibling is named explicitly.

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 clause 'so long jobs are not reaped while they run' implies the use case (extending TTL before a long-running job), but there is no explicit when-to-use/when-not guidance, no mention of alternatives, and no stated precondition such as the sandbox being in a running state beyond the adjective 'running'.

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