Skip to main content
Glama

Sandboxd Code Run

Runs Python, JavaScript or TypeScript code in an isolated one-shot sandbox and r

execute-code

Runs Python, JavaScript or TypeScript code in an isolated one-shot sandbox and returns stdout, stderr, exit code and artifacts (Daytona CodeRunRequest/ExecuteResponse compatible) Price: $0.002 a call (3 free calls a day without an API key).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
envNoEnvironment variables; keys must match [A-Za-z_][A-Za-z0-9_]* (Daytona's rule)
argvNoCommand-line arguments for the program (sys.argv[1:] in Python, process.argv.slice(2) in Node)
codeYesThe code to run (up to 1 MB of UTF-8)
filesNoText files written into the work directory next to the program (up to 50, 1 MB each, 4 MB total); the entry point main.py/main.js/main.ts is reserved
outputsNoRelative paths to read back after the run (up to 20); up to 1 MB each comes back base64 in outputFiles, larger in tooLargeOutputs, absent in missingOutputs
timeoutNoRun timeout in seconds, 1-120 (default 60); a timed-out run answers exitCode 124
languageYes"python", "javascript" or "typescript"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden, and it delivers real behavioral facts: one-shot isolated execution, the return payload (stdout, stderr, exit code, artifacts), and the pricing/free-tier auth model. It omits permission requirements and concurrency/rate-limit behavior beyond the free-call count, keeping it below a 5.

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 purpose is front-loaded in a single dense sentence with the return contract immediately after, so there is little waste. The trailing pricing clause is useful but slightly promotional, preventing a 5.

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 no output schema, the description helpfully enumerates the return values, and with 100% schema coverage the inputs are fully specified elsewhere. The one clear gap is sibling differentiation, which leaves the definition just short of complete.

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 100%, so every parameter is already documented in the schema. The description adds no parameter-level detail (e.g., timeout or output semantics) beyond what the schema provides, making the baseline 3 correct.

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?

States a specific verb+resource ('Runs ... code in an isolated one-shot sandbox') and names the supported languages, which is far more than a tautology. It does not differentiate itself from the sibling execute-command, so it stops short of a 5.

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?

There is no guidance on when to use this tool versus the sibling execute-command, nor any stated preconditions for calling it. The pricing line describes cost, not usage context, so an agent gets no routing help.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources