Skip to main content
Glama

thanaton_attach_volume

Attach a persistent sparse ext4 volume to a microVM sandbox at /data so data persists across scale-to-zero snapshots and hibernation.

Instructions

Attach a persistent sparse ext4 volume mounted at /data with scale-to-zero snapshot persistence.

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_attach_volume"
  }
}

Input Schema

NameRequiredDescriptionDefault
size_gbNoVirtual volume size in gigabytes (default: 10)
mount_pathNoTarget mount path inside microVM (default: /data)
sandbox_idYesMicroVM sandbox ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.6

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does add real context: the volume is sparse, ext4, and survives scale-to-zero via snapshots. It omits what happens if mount_path already contains data, whether the call creates a new volume or reattaches an existing one, size limits, and whether the sandbox must be running.

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 sentence with no filler, front-loading the verb and resource before the mount and persistence traits. Nothing is redundant.

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 three-parameter mutation with no annotations and no output schema, the description establishes the resource model but leaves key operational facts (error behavior, return value, reattach semantics, sandbox-state requirements) unstated.

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% and each parameter already has a description, so the baseline is 3. The description's mention of /data echoes the mount_path default and 'sparse' hints at size_gb semantics, but adds no syntax or constraint 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?

The description uses a specific verb ('Attach') and a precise resource ('persistent sparse ext4 volume'), and pins the default mount point at /data. It is clearly distinguishable from listing tools like thanaton_get_volumes, but it never says how it relates to sandbox lifecycle siblings such as spawn_sandbox or destroy_sandbox.

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 guidance, no prerequisites (e.g. the sandbox must already exist), and no exclusions or alternative named. The agent must infer that this is the tool to call when persistence across scale-to-zero is wanted.

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