rent.dev

Pause a sandbox

rent_pause_sandbox

Idempotent

Pauses a running sandbox, keeping its memory and files; the id stays valid and rent_resume_sandbox continues it.

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": "rent_pause_sandbox"
  }
}

Input Schema

Name	Required	Description	Default
`sandbox_id`	Yes	Sandbox id (`lse_…`) from rent_create_sandbox or rent_list_sandboxes. It names the sandbox for its whole life and keeps answering rent_get_sandbox, with the final state, after it ends.

Output Schema

Name	Required	Description	Default
`id`	Yes
`wire`	Yes
`state`	Yes
`domain`	Yes
`region`	Yes
`ended_at`	Yes
`metadata`	Yes
`supplier`	Yes
`template`	Yes
`billed_by`	Yes
`cpu_count`	Yes
`memory_mb`	Yes
`account_id`	Yes
`auto_pause`	Yes
`created_at`	Yes
`sandbox_id`	Yes
`started_at`	Yes
`timeout_at`	Yes
`auto_resume`	Yes
`endpoint_id`	Yes
`held_micros`	Yes
`captured_micros`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and idempotentHint=true; the description adds real value on top by confirming that memory and files survive and that the sandbox id remains valid after the call. It does not address what happens to in-flight processes or whether a paused sandbox continues to accrue cost, which is the main open behavioral question for a pause operation.

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 its effect, with zero filler. Every clause (memory/files retained, id validity, resume path) carries distinct information.

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?

With an output schema present, the return value needs no explanation, annotations cover the safety profile, and the single parameter is fully documented in the schema. The only gap is the cost/process side effect of pausing, which leaves the definition slightly short of fully complete for a lifecycle-mutating tool.

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, and the schema already explains the `lse_…` id format, its provenance (rent_create_sandbox / rent_list_sandboxes) and its lifetime. The description adds nothing about the parameter itself, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Pauses') and resource ('a running sandbox') plus the resulting state ('keeping its memory and files'). The phrase 'the id stays valid' implicitly separates it from termination, so an agent can tell it apart from rent_terminate_sandbox and rent_resume_sandbox without opening another schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It clearly signals the pause/resume pairing by naming rent_resume_sandbox as the continuation path, which gives the agent an actionable next step. It stops short of stating when not to pause — for example, when the goal is to free resources permanently (rent_terminate_sandbox) — so there is no explicit exclusion.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All rent.dev tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?