Skip to main content
Glama

code_execute

Execute Python or JavaScript code in a sandbox to test scripts, debug algorithms, or run isolated code snippets safely.

Instructions

Execute Python or JavaScript code in a sandbox ($0.01)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeYes
languageNopython

Implementation Reference

  • index.js:45-45 (registration)
    Registration of the code_execute tool in the TOOLS array.
    { name: 'code_execute', description: 'Execute Python or JavaScript code in a sandbox', inputSchema: { type: 'object', properties: { code: { type: 'string' }, language: { type: 'string', enum: ['python', 'javascript'], default: 'python' } }, required: ['code'] }, endpoint: '/code/execute', price: '$0.01' },
  • index.js:50-79 (handler)
    Generic callTool function that executes API requests for all tools, including code_execute.
    async function callTool(endpoint, params) {
      const fetch = (await import('node-fetch')).default;
      const isGet = ['GET'].includes((TOOLS.find(t => t.endpoint === endpoint) || {}).method);
      
      const url = isGet 
        ? `${BASE_URL}${endpoint}?${new URLSearchParams(params)}`
        : `${BASE_URL}${endpoint}`;
      
      const res = await fetch(url, {
        method: isGet ? 'GET' : 'POST',
        headers: {
          'Content-Type': 'application/json',
          'Authorization': `Bearer ${API_KEY}`,
        },
        body: isGet ? undefined : JSON.stringify(params),
      });
      
      const text = await res.text();
      let data;
      try { data = JSON.parse(text); } catch { data = { raw: text }; }
      
      if (!res.ok) {
        if (res.status === 402) {
          throw new Error(`Insufficient credits. Add credits at https://iteratools.com. Cost: ${TOOLS.find(t=>t.endpoint===endpoint)?.price || 'see docs'}`);
        }
        throw new Error(`API error ${res.status}: ${text.substring(0, 200)}`);
      }
      
      return data;
    }
Behavior3/5

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

With no annotations, description carries full burden. Mentions 'sandbox' (isolation) and cost, but omits critical execution details: timeout limits, available libraries/packages, output format (stdout vs return value), and file system persistence.

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?

Single sentence, front-loaded with action verb, zero redundancy. Every element (action, languages, environment, cost) conveys essential information efficiently.

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 high-complexity operation (arbitrary code execution) with no annotations, no output schema, and minimal schema coverage, the description is insufficient. Missing: security boundaries, resource limits, package availability, and execution lifecycle details.

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 has 0% description coverage. Description compensates partially by specifying the two supported languages (aligning with the enum), implying 'code' parameter content, but does not explicitly document parameter semantics or required syntax.

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?

Clear specific verb ('Execute') and resource ('Python or JavaScript code'). Explicitly distinguishes from all siblings (image processing, PDF, search, etc.) by specifying code execution capability.

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?

Provides implicit usage context (run code) and cost constraint ($0.01), but lacks explicit guidance on when to choose Python vs JavaScript, timeout limits, or alternatives to using this tool.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/fredpsantos33/itera-tools-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server