rent.dev

Get a sandbox

rent_get_sandbox

Read-onlyIdempotent

One sandbox by id: state (requested, placing, running, paused, settling, terminated, failed), template, size, timeout_at, port-URL domain, and what it has been charged and holds.

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_get_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

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description contributes the state vocabulary (requested through failed), which helps an agent interpret results, but it does not discuss what happens on unknown/expired ids or any access constraints. Adding a useful detail on top of thorough annotations lands at 3.

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?

A single front-loaded sentence with the resource named first and the returned fields packed into a tight colon construction. Nothing is padded and nothing is missing from the sentence's scope.

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 read tool with full annotations and an output schema, the definition is essentially sufficient: what it fetches and the shape of the payload are both clear. The only shortfall is the absence of guidance about which companion tool answers related questions.

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?

Only one parameter, and the schema documents it at 100% coverage including its origin and lifetime semantics. The description adds nothing about the id beyond what the schema says, so the 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?

"One sandbox by id" gives a specific verb-and-resource pair, and the sentence then enumerates exactly what is returned (state, template, size, timeout_at, port-URL domain, billing/holds). The singular scoping implicitly separates it from rent_list_sandboxes, but no sibling is named, so it falls short of the top mark.

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?

The definition implies usage (fetch the current view of a single sandbox) but never states when to reach for this versus rent_list_sandboxes or rent_get_usage, nor any exclusions or prerequisites. The one useful usage note, that the sandbox id keeps resolving after termination, lives in the schema rather than the description.

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?