Skip to main content
Glama
freecad-mcp-headless

freecad-mcp-headless

by pitbuild

open_document

Opens a CAD file from an allowed directory and makes it the active document, supporting FCStd, STEP, IGES, BREP, STL, OBJ, 3MF, DXF, SVG, and AMF.

Instructions

Open a CAD file and make it the active document.

Supports .FCStd, .step/.stp, .iges/.igs, .brep, .stl, .obj, .3mf, .dxf, .svg, .amf. The file must live inside an allowed directory. Returns the document name, object count and the FreeCAD types it contains.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "path": "<path>"
    },
    "name": "open_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It does disclose a real side effect (the document becomes active) and the returned fields, but it never says what happens when a document of that name is already open, whether the call is idempotent, or why the optional name parameter exists.

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?

Three short sentences with the action and state change front-loaded, followed by the format enumeration and the location constraint. Nothing is redundant, and the format list is genuinely decision-relevant rather than filler.

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

Completeness3/5

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

For a two-parameter mutation-style tool with no annotations and no output schema, the description covers the return shape and one key constraint, which is more than many peers. It still leaves the name parameter and the name-collision behavior undocumented, which is a meaningful gap for a tool that mutates application state.

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

Parameters2/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 and does so only partially: it constrains the path (must be inside an allowed directory) and lists accepted extensions. The 'name' parameter is never mentioned at all, leaving its purpose entirely unexplained.

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?

States a specific verb and resource ('Open a CAD file and make it the active document') and enumerates the supported formats, so an agent can tell it apart from close_document, save_document, and inspect_document without opening any schema.

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?

Usage is implied rather than stated: it is the entry point for loading a file, and the allowed-directory constraint tells the agent one precondition. However, no alternative is named (e.g., when to prefer inspect_document for metadata only) and no exclusion is given.

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