Skip to main content
Glama
LBurny

CADPilot

by LBurny
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

execute_code

Execute Python scripts within FreeCAD to drive parametric modeling and geometry operations. Optionally attach a screenshot to confirm the result.

Instructions

Execute arbitrary Python code in FreeCAD.

The code runs on FreeCAD's GUI thread with the full FreeCAD Python API
available (FreeCAD, FreeCADGui already imported; import Part/Draft/etc.
as needed). print() output is captured and returned.

Args:
    code: The Python code to execute.
    with_screenshot: Attach a screenshot after successful execution
        (default: no screenshot).

Returns:
    A message indicating the success or failure of the code execution, the
    output of the code execution, and a screenshot only when requested.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeYes
with_screenshotNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A4.4/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 covers key behaviors: execution on the GUI thread, pre-imported modules, captured print output, conditional screenshot, and the return structure. It does not mention risks like GUI freezing but still provides substantial transparency.

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 with Args and Returns sections, and every sentence adds value. It is slightly longer than necessary, but the organization and front-loading make it easy to scan.

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?

Given the tool's complexity, the description covers the execution environment, output handling, screenshot option, and return format. The presence of an output schema makes return details redundant but harmless. Overall, it is complete enough for an agent to use 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?

Schema description coverage is 0%, so the description must compensate. It explains 'code' as the Python code to execute and 'with_screenshot' as attaching a screenshot after successful execution with a default of no screenshot, matching the schema's type and default.

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 'Execute arbitrary Python code in FreeCAD' with a specific verb and resource. It also specifies the execution context (GUI thread) and distinguishes from the asynchronous sibling by implying synchronous execution with captured output.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context for when to use the tool: to run Python code in FreeCAD with the full API and capture print output. It does not explicitly mention alternatives or exclusions, but the context is sufficient for most scenarios.

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/LBurny/cadpilot'

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