Skip to main content
Glama

thanaton_sleep_sandbox

Hibernate a running MicroVM sandbox to an NVMe snapshot, reducing CPU usage and cost to zero while preserving RAM state for later wake-up.

Instructions

Scale a MicroVM to zero (hibernates RAM to NVMe snapshot, 0% CPU consumption, $0 cost).

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

Input Schema

NameRequiredDescriptionDefault
sandbox_idYesThe ID of the running sandbox to put to sleep

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.6

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses the mechanism (RAM hibernated to NVMe) and the resource effect (0% CPU, $0 cost), but says nothing about reversibility, how or when to wake, latency, idempotency on an already-sleeping sandbox, or whether in-flight connections are dropped.

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 sentence, front-loaded with the action, and the parenthetical carries only genuinely useful facts about cost and state preservation. No filler or repetition.

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 single-parameter state-mutating tool with no annotations and no output schema, the description covers the action and its cost/state consequences but leaves the wake path, failure modes, and return value unaddressed. Adequate to call, not adequate to use confidently.

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?

There is a single parameter and schema coverage is 100%; the schema already states 'The ID of the running sandbox to put to sleep.' The description adds no new meaning to sandbox_id, so the baseline of 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 and resource ('Scale a MicroVM to zero') plus the operational result, which is far more specific than the bare tool name. It does not name a sibling, so the agent must infer the contrast with thanaton_destroy_sandbox and thanaton_wake_sandbox from the 'sleep' framing alone.

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: 'hibernates RAM to NVMe snapshot' signals a reversible pause rather than deletion, which weakly distinguishes it from destroy, and it never names wake_sandbox as the counterpart. There is no explicit when-to-use, when-not-to-use, or precondition statement.

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