Skip to main content
Glama

thanaton_wake_sandbox

Wakes a sleeping or hibernated MicroVM from an NVMe memory snapshot in sub-6 ms, enabling AI agents to resume isolated execution sandboxes without local setup.

Instructions

Instantly wake a sleeping/hibernated MicroVM from NVMe memory snapshot in sub-6ms (<2ms with UFFD lazy-paging).

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

Input Schema

NameRequiredDescriptionDefault
sandbox_idYesThe ID of the sleeping sandbox to wake

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?

No annotations are supplied, so the description carries the full behavioral burden. It does disclose genuinely useful traits (NVMe memory snapshot restore, sub-6ms latency, <2ms with UFFD lazy-paging), but says nothing about whether the previous in-memory state is fully preserved, authorization requirements, or failure modes for a non-sleeping or missing sandbox.

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 action and the performance characteristics arrive immediately, and nothing is repeated or padded.

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 one-parameter tool with no output schema and no annotations, the definition covers the essentials: what it does, the required input, and the performance profile. Only precondition handling and state-preservation guarantees are missing, which are minor for this complexity level.

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 with 100% schema description coverage ('The ID of the sleeping sandbox to wake'), so the schema already does the work and the baseline of 3 applies. The description adds no format, prefix, or sourcing detail beyond what the schema provides.

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 ('wake') against a specific resource ('sleeping/hibernated MicroVM'), and the qualifier 'sleeping/hibernated' implicitly separates it from sleep_sandbox, spawn_sandbox and destroy_sandbox. It stops short of naming an alternative, so differentiation is inferred rather than stated.

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 caller must supply a 'sandbox_id' of a sleeping sandbox, so the condition for use is that a sandbox is hibernated. There is no explicit when-to-use/when-not statement, no mention of what happens if the sandbox is already awake, and no pointer to spawn_sandbox as the alternative for creating a new one.

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