Skip to main content
Glama

A2A Defense & Monetization Gateway

execute_sandboxed_computation

Ejecuta un script de código Python en un runtime aislado determinista con límites RLIMIT de memoria y CPU.

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": {
      "code": "<code>"
    },
    "name": "execute_sandboxed_computation"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYes
max_memory_mbNo
timeout_secondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses that execution is isolated, deterministic, and bounded by RLIMIT memory/CPU caps, which is real behavioral context. It omits critical traits: whether filesystem/network access exists, what happens when limits are exceeded, and whether errors raise or return.

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?

A single dense sentence with the core purpose front-loaded and no filler. Brevity here costs coverage elsewhere, but the sentence itself earns its place.

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?

No annotations, no output schema, and 0% parameter coverage mean the description must do more. It never states what the tool returns (stdout, exit code, captured errors) or what the caller must supply, leaving an agent unable to predict the response shape for a code-execution tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must explain all three parameters. It only gestures at memory and CPU limits via 'límites RLIMIT', leaving 'code' (the sole required parameter) and the distinction between max_memory_mb and timeout_seconds entirely undocumented, along with defaults and valid ranges.

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 and resource ('Ejecuta un script de código Python') plus the execution environment (isolated deterministic runtime with RLIMIT limits). An agent knows exactly what the tool does, though it offers no differentiation from sibling tools (most of which are unrelated anyway).

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?

No when-to-use or when-not-to-use guidance, no preconditions, and no routing to alternatives. The description never says what kinds of tasks warrant sandboxed execution versus another tool.

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