Skip to main content
Glama
csakaszamok

Purgatory (p7y)

Official
by csakaszamok
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

create_sandbox

Create sandbox HTTP POST /sandboxes

Instructions

Create sandbox HTTP POST /sandboxes

Input Schema

NameRequiredDescriptionDefault
cpusNoCPU limit (cores). Default SANDBOX_CPUS; users up to SANDBOX_MAX_CPUS, the admin up to the host.
nameYes
memoryNoMemory limit (512m, 4g). Default SANDBOX_MEMORY; users up to SANDBOX_MAX_MEMORY, the admin up to the host.
composeNoUse this compose text instead of the template's compose.yaml (the template's before_script and defaults still apply). GET /templates/:name gives the template's text to start from. At most 256 KB.
runtimeNoHow the sandbox runs (GET /runtimes). Omit for DEFAULT_RUNTIME (auto: sysbox where installed, else dind).
ssh_keysNoExtra SSH public keys for this sandbox only (your keys from /ssh-keys always get in)
templateNoWhat runs inside (GET /templates). Omit for DEFAULT_TEMPLATE (starter).
idle_timeoutNoStop the sandbox after this long without HTTP traffic; the next request wakes it. Days are kept as hours (1d = 24h). 0 or off = never. Omit for template idle_timeout (default 30m).
deep_sleep_afterNoTake the sandbox down (containers + network freed, data kept) after it has been stopped this long; the next request rebuilds it. "off" disables. Omit for template deep_sleep_after (default 7d).
create_inner_stackNoWhether to deploy the inner docker-compose stack defined in the template

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.11.3
    • changedInput schema / properties / idle_timeout / description
      Previous value: -"Stop the sandbox after this long without HTTP traffic; the next request wakes it. 0 or off = never. Omit for template idle_timeout (default 30m)."New value: +"Stop the sandbox after this long without HTTP traffic; the next request wakes it. Days are kept as hours (1d = 24h). 0 or off = never. Omit for template idle_timeout (default 30m)."
    • changedInput schema / properties / idle_timeout / pattern
      Previous value: -"^([1-9][0-9]*(s|m|h)|0|off)$"New value: +"^([1-9][0-9]*(s|m|h|d)|0|off)$"
  2. First observedv0.7.1

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the full behavioral burden. It only says this creates a sandbox via POST; it does not disclose permissions, quota/limit behavior, side effects, defaults applied from templates, or what the response contains.

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?

The description is very short and front-loaded with the main action. However, the second line is mostly endpoint metadata and does not contribute much additional understanding for an agent.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 10-parameter mutation tool with no annotations and no output schema, the description is too thin. The schema documents most parameters well, but the description does not explain creation behavior, return value, or important side effects an agent should know before invoking it.

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 high at 90%, with detailed descriptions for most parameters such as cpus, memory, compose, runtime, and sleep settings. The tool description itself adds no parameter semantics, so the baseline of 3 is appropriate.

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 names a specific verb and resource ("Create sandbox") and even maps it to the HTTP endpoint. It is clear what the tool does, but it does not distinguish it from related sibling tools such as create_sandbox_folder or create_token.

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?

The description gives no guidance on when to use this tool versus alternatives, nor does it state prerequisites, constraints, or when not to use it. The HTTP method/endpoint is implementation detail rather than usage guidance.

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