Skip to main content
Glama

thanaton_get_volumes

Lists persistent ext4 sparse volumes attached to a microVM sandbox, enabling SQLite, PocketBase, or local file storage to survive scale-to-zero hibernation.

Instructions

List persistent ext4 sparse volumes attached to a microVM sandbox for SQLite, PocketBase, or local file storage with scale-to-zero persistence.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "thanaton_get_volumes"
  }
}

Input Schema

NameRequiredDescriptionDefault
sandbox_idNoMicroVM sandbox ID (default: sbx-default)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.6

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the burden. It does disclose meaningful behavior beyond the name: volumes are persistent, ext4, sparse, and survive scale-to-zero. It does not state that the operation is read-only, what permissions are needed, or what happens when no volumes exist.

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?

One dense but well-formed sentence with the action front-loaded and no redundant wording. The trailing use-case clause is slightly marketing-flavored but still informative.

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 read tool this covers the essentials of what is listed, but with no output schema the description never indicates what a volume record contains (mount path, size, attachment state), which an agent would need to act on the results.

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% for the single sandbox_id parameter, including the default, so the schema already does the work. The description adds no context about how sandbox_id scopes the listing or what the default resolves to, so baseline 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?

The description gives a specific verb ('List') and a precise resource ('persistent ext4 sparse volumes attached to a microVM sandbox'), plus the intended payloads (SQLite, PocketBase, local files). It does not explicitly distinguish itself from the sibling thanaton_attach_volume, but the read/list framing is unambiguous.

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?

Use cases (SQLite, PocketBase, local file storage with scale-to-zero persistence) imply when to reach for this tool, but there is no explicit when-to-use/when-not guidance and no named alternative for related operations such as attaching or reaping volumes.

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