Skip to main content
Glama

thanaton_destroy_sandbox

Terminates processes and tears down TAP interfaces, cgroups, and sandbox resources to reclaim all allocated resources for a given sandbox ID.

Instructions

Terminate processes, tear down TAP network interface, cgroups, and reclaim all sandbox resources.

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

Input Schema

NameRequiredDescriptionDefault
sandbox_idYesThe ID of the sandbox to destroy

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.6

TDQS

A3.6/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 behavioral burden, and it does disclose what is destroyed (processes, TAP interface, cgroups, all resources) - genuinely useful context. However, it omits irreversibility, whether attached volumes or secrets survive, idempotency on an already-destroyed sandbox, and permission requirements, which matter greatly 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One front-loaded sentence with zero filler; the destruction scope comes first and every clause names a distinct resource being reclaimed.

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 one-parameter, no-output-schema tool this is nearly sufficient, but a destructive operation should state reversibility and side effects on dependent resources (volumes, secrets, logs) that `reclaim all sandbox resources` only vaguely gestures at.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Single required parameter with 100% schema description coverage, so the schema already defines sandbox_id. The description adds no additional parameter meaning, but with one fully-documented param the baseline is high and there is no ambiguity about which identifier is consumed.

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 concrete verb set (terminate, tear down, reclaim) against a specific resource (the sandbox), and enumerates the components affected: processes, TAP network interface, cgroups. This is far more specific than the name alone, though it never explicitly contrasts itself with thanaton_sleep_sandbox or thanaton_rollback, leaving the agent to infer the irreversibility distinction.

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?

Usage is only implied: the destructive verb set signals 'permanent teardown' versus a suspend or rollback, but the description never says when to choose this over sleep_sandbox, whether the sandbox must be stopped first, or what to do if teardown fails. No exclusions or preconditions are stated.

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

Deploy Server

Other Tools