Skip to main content
Glama
mario-2015

FreeCAD MCP Connector

by mario-2015

create_object

Creates new Part, Draft, PartDesign, or FEM objects in a FreeCAD document by specifying type and properties, returning a screenshot for verification.

Instructions

Create a new object in FreeCAD. Object type is starts with "Part::" or "Draft::" or "PartDesign::" or "Fem::".

Args: doc_name: The name of the document to create the object in. obj_type: The type of the object to create (e.g. 'Part::Box', 'Part::Cylinder', 'Draft::Circle', 'PartDesign::Body', etc.). obj_name: The name of the object to create. obj_properties: The properties of the object to create. include_screenshot: Whether to return a screenshot of the model (default True). Set to False to save tokens when visual feedback is not needed, e.g. for intermediate steps in a longer sequence of changes. view_name: The view orientation of the returned screenshot (default "Isometric"). Pick the view that best shows the change being made.

Returns: A message indicating the success or failure of the object creation and a screenshot of the object.

Examples: If you want to create a cylinder with a height of 30 and a radius of 10, you can use the following data. json { "doc_name": "MyCylinder", "obj_name": "Cylinder", "obj_type": "Part::Cylinder", "obj_properties": { "Height": 30, "Radius": 10, "Placement": { "Base": { "x": 10, "y": 10, "z": 0 }, "Rotation": { "Axis": { "x": 0, "y": 0, "z": 1 }, "Angle": 45 } }, "ViewObject": { "ShapeColor": [0.5, 0.5, 0.5, 1.0] } } }

If you want to create a circle with a radius of 10, you can use the following data.
```json
{
    "doc_name": "MyCircle",
    "obj_name": "Circle",
    "obj_type": "Draft::Circle",
}
```

If you want to create a FEM analysis, you can use the following data.
```json
{
    "doc_name": "MyFEMAnalysis",
    "obj_name": "FemAnalysis",
    "obj_type": "Fem::AnalysisPython",
}
```

If you want to create a FEM constraint, you can use the following data.
```json
{
    "doc_name": "MyFEMConstraint",
    "obj_name": "FemConstraint",
    "obj_type": "Fem::ConstraintFixed",
    "analysis_name": "MyFEMAnalysis",
    "obj_properties": {
        "References": [
            {
                "object_name": "MyObject",
                "face": "Face1"
            }
        ]
    }
}
```

If you want to create a FEM mechanical material, you can use the following data.
```json
{
    "doc_name": "MyFEMAnalysis",
    "obj_name": "FemMechanicalMaterial",
    "obj_type": "Fem::MaterialCommon",
    "analysis_name": "MyFEMAnalysis",
    "obj_properties": {
        "Material": {
            "Name": "MyMaterial",
            "Density": "7900 kg/m^3",
            "YoungModulus": "210 GPa",
            "PoissonRatio": 0.3
        }
    }
}
```

If you want to create a FEM mesh, you can use the following data.
The `Shape` property is required (legacy `Part` is also accepted).
On FreeCAD 1.x the size limits are `CharacteristicLengthMax/Min`;
the legacy `ElementSizeMax/Min` keys are also accepted.
```json
{
    "doc_name": "MyFEMMesh",
    "obj_name": "FemMesh",
    "obj_type": "Fem::FemMeshGmsh",
    "analysis_name": "MyFEMAnalysis",
    "obj_properties": {
        "Shape": "MyObject",
        "CharacteristicLengthMax": 10,
        "CharacteristicLengthMin": 0.1
    }
}
```

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
doc_nameYes
obj_nameYes
obj_typeYes
view_nameNoIsometric
analysis_nameNo
obj_propertiesNo
include_screenshotNo
Behavior3/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does mention the return format ('a message indicating the success or failure... and a screenshot'), the purpose of view_name, and version-specific behavior for FEM mesh size limits. However, it does not disclose potential side effects such as whether an existing object with the same name is overwritten, whether the document must exist, or error handling behavior. This leaves gaps in transparency for a mutation tool.

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 lengthy but well-structured with clear sections for Args, Returns, and Examples. Each example serves a distinct purpose (cylinder, circle, FEM analysis, constraint, material, mesh). The length is justified by the tool's complexity, and the structure makes it easy to scan. It could be trimmed slightly, but it remains efficient and purposeful.

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 (7 parameters, nested objects, multiple object types, no output schema, no annotations), the description is remarkably complete. It covers all parameter semantics, return values, special notes for FEM mesh (including FreeCAD 1.x key differences), and provides extensive examples. The only minor issue is the omission of analysis_name from the Args list, which is still evident from examples. This is a comprehensive description for a complex tool.

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

Parameters4/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 doc_name, obj_type, obj_name, obj_properties, include_screenshot, and view_name in the Args section, and provides detailed examples for each parameter, including nested obj_properties. However, analysis_name, which appears in the schema and examples, is missing from the Args list, leaving a minor gap. Overall, the description adds significant meaning beyond the bare schema.

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 its purpose: 'Create a new object in FreeCAD.' It specifies the verb 'create', the resource 'new object', and narrows the scope by enumerating valid type prefixes like 'Part::', 'Draft::', 'PartDesign::', and 'Fem::'. This distinguishes it from sibling tools like create_document (which creates documents) and edit_object (which edits existing objects).

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 gives clear context on when to use the tool (creating objects of various types) and includes practical advice, such as setting include_screenshot to False for intermediate steps to save tokens. However, it does not explicitly contrast this tool with alternatives like edit_object or delete_object, nor does it state situations where this tool should NOT be used. It provides clear context but no explicit exclusions.

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/mario-2015/freecad-mcp-connector-for-claude-desktop'

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