Skip to main content
Glama
freecad-mcp-headless

freecad-mcp-headless

by pitbuild

screenshot

Render CAD models to PNG or SVG without a display or GPU, choosing orthographic views and including bounding-box dimensions in millimetres.

Instructions

Render the model to a PNG (or SVG) without a display or GPU.

Views: iso, front, back, left, right, top, bottom. The image is an orthographic, flat-shaded projection of the tessellated geometry, annotated with the bounding-box size in millimetres.

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": "screenshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
viewNoiso
widthNo
heightNo
documentNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It does disclose meaningful behavior: output formats, the seven available views, orthographic flat-shaded projection, and bounding-box annotation burned into the image. It omits other important traits — that a required path means a file is written (and whether an existing file is overwritten), and whether a document must already be loaded/open.

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?

Two short blocks: the action first, then the view list and rendering characteristics. Every sentence carries information and nothing is padded. Minor cost is the slightly jargon-heavy 'tessellated geometry' phrasing, but it is not wasted space.

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 five-parameter, no-output-schema, no-annotation tool, the description covers the output artifact and views well. It is incomplete on prerequisites (is a document open? what does `document` select?), on file-overwrite behavior for `path`, and on how width/height affect the result.

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

Parameters3/5

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

Schema description coverage is 0% for five parameters, so the description must compensate. It does add real value for `view` by enumerating the seven legal values where the schema offers no enum, and it implies format selection via PNG/SVG. It says nothing about `width`, `height`, or `document`, leaving three of five parameters undocumented anywhere.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The first sentence gives a specific verb and output artifact: render the model to PNG/SVG, headlessly (no display or GPU). That is far more than a restatement of the name. It stops short of distinguishing itself from the sibling export_document, so an agent must still guess which of the two to reach for.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance and no named alternative. The phrase 'without a display or GPU' implies a headless/offline context, and listing the seven views hints at how it is used, but the agent is left to infer when this is preferable to export_document or how it relates to open_document/inspect_document.

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