Execute Python code or scripts directly from AI assistants, supporting virtual environments and command-line arguments for automated development tasks.
Execute Python code or script
| Name | Required | Description | Default |
|---|---|---|---|
| code | No | Python code to execute | |
| script_path | No | Path to Python script file | |
| args | No | Command line arguments | |
| venv | No | Path to virtual environment |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, leaving the description fully responsible for behavioral disclosure. It only says 'Execute' without mentioning safety, side effects, environment isolation, or security restrictions.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is very short (one phrase) but lacks substantive content. It is not verbose, but it is under-specified for an execution tool with four optional parameters.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the absence of an output schema and annotations, the description should cover execution environment, parameter interactions, and return behavior. It does not, leaving significant gaps for an execution tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% with individual parameter descriptions. The tool description adds no additional meaning beyond the schema, achieving the baseline for this dimension.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description 'Execute Python code or script' clearly states the action and resource, but does not differentiate from sibling tools like run_command or run_javascript. It is adequate but lacks specificity.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool versus alternatives (e.g., run_command for generic commands, pip_install for package management). The description provides no context for tool selection.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.