Skip to main content
Glama
maxim-saplin

Safe Local Python Executor/Interpreter

run_python

Execute Python code in a secure sandbox environment for calculations and data manipulation. The tool runs simple Python scripts with restricted imports and returns results with logs.

Instructions

Execute Python code in a secure sandbox environment.

This tool allows running simple Python code for calculations and data manipulations.
The execution environment is restricted for security purposes. Make sure you create a single file
that can be executed in one go and it returns a result.

Default allowed imports:
- math
- random 
- datetime
- time
- json
- re
- string
- collections
- itertools
- functools
- operator

Args:
    code: The Python code to execute. Must be valid Python 3 code. The result must be stored in a variable called `result`. E.g.:
    ```python
    import math
    result = math.sqrt(16)
    ```
    
Returns:
    A dictionary with execution results containing:
    - result: The final value or None if no value is returned
    - logs: Any output from print statements

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The core handler function for the 'run_python' tool. It is registered via the @mcp.tool() decorator. Executes the provided Python code using a LocalPythonExecutor sandbox and returns the result and logs. The docstring provides the input/output schema details.
    @mcp.tool()
    async def run_python(
        code: str
    ) -> Dict[str, Any]:
        """Execute Python code in a secure sandbox environment.
        
        This tool allows running simple Python code for calculations and data manipulations.
        The execution environment is restricted for security purposes. Make sure you create a single file
        that can be executed in one go and it returns a result.
    
        Default allowed imports:
        - math
        - random 
        - datetime
        - time
        - json
        - re
        - string
        - collections
        - itertools
        - functools
        - operator
        
        Args:
            code: The Python code to execute. Must be valid Python 3 code. The result must be stored in a variable called `result`. E.g.:
            ```python
            import math
            result = math.sqrt(16)
            ```
            
        Returns:
            A dictionary with execution results containing:
            - result: The final value or None if no value is returned
            - logs: Any output from print statements
        """
        logger.info(f"Executing Python code: {code}")
        
        result, logs, _ = executor(code)
    
        response = {
            "result": result,
            "logs": logs
        }
        
        logger.info(f"Execution result: {result}")
        return response
  • Initialization of the LocalPythonExecutor used by the run_python tool to safely execute Python code.
    executor = LocalPythonExecutor(additional_authorized_imports=[])
    executor.send_tools({})
  • mcp_server.py:24-24 (registration)
    Creation of the FastMCP server instance named 'python-executor', to which tools like run_python are registered.
    mcp = FastMCP("python-executor")
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively describes key traits: the secure sandbox environment, restrictions for security, requirement to create a single executable file, and default allowed imports. However, it doesn't cover aspects like execution time limits, memory constraints, or error handling, leaving some behavioral gaps.

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 description is well-structured and front-loaded with the core purpose, followed by usage notes, allowed imports, parameter details, and return information. It's appropriately sized for the tool's complexity, but the list of allowed imports and code example add some length that could be streamlined without losing clarity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (code execution with security constraints), no annotations, and an output schema that documents return values, the description is highly complete. It covers purpose, behavioral traits, parameter semantics with examples, and usage context, leaving minimal gaps for an AI agent to understand and invoke the tool correctly.

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

Parameters5/5

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

The input schema has 0% description coverage, so the description must fully compensate. It adds substantial meaning beyond the schema by detailing the 'code' parameter: it must be valid Python 3 code, require storing results in a variable called 'result', and includes a clear example with syntax and usage. This provides comprehensive semantic context for the single parameter.

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?

The description clearly states the tool's purpose: 'Execute Python code in a secure sandbox environment' with specific verbs ('execute', 'run') and resource ('Python code'). It distinguishes the tool's scope by mentioning it's for 'simple Python code for calculations and data manipulations' and operates in a restricted environment, making its function unambiguous even without siblings.

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 description implies usage context by specifying it's for 'simple Python code for calculations and data manipulations' and mentions security restrictions, but it lacks explicit guidance on when to use this tool versus alternatives (e.g., other code execution tools or manual methods). No siblings are listed, so differentiation isn't needed, but general usage context is only partially addressed.

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/maxim-saplin/mcp_safe_local_python_executor'

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