Skip to main content
Glama
freecad-mcp-headless

freecad-mcp-headless

by pitbuild

measure

Calculates geometry metrics in millimetres—volume, surface area, centre of mass, bounding box, diagonal, and face/edge/vertex counts—per object or summed for selected objects.

Instructions

Measure geometry in millimetres.

Returns volume (mm3), surface area (mm2), centre of mass, bounding box, diagonal and face/edge/vertex counts — per object and summed. Pass objects to restrict the measurement to selected object names.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "measure"
  }
}

Input Schema

NameRequiredDescriptionDefault
objectsNo
documentNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose valuable behavior: explicit units (mm, mm3, mm2), the exact set of returned metrics, and that results are reported per object and summed. It does not state whether a document must be open or active, whether the call mutates state (implicitly read-only via "measure" but unconfirmed), or what happens when no objects match.

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?

Front-loaded with the core action and unit, then a compact enumeration of outputs, then the one parameter hint. Two short paragraphs, no filler; the metrics list is long but each item earns its place since no output schema exists.

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?

Return values are covered thoroughly, which is the main gap given there is no output schema. However, for a two-parameter tool with zero schema description coverage and no annotations, leaving document unexplained and omitting document-state requirements means the agent lacks what it needs to call this reliably in a multi-document session.

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 coverage is 0%, so the description must compensate. It does add real meaning for objects — that it restricts the measurement to selected object names — but the second parameter, document, is never mentioned in the description or the schema, leaving an undocumented argument that likely governs which document is measured.

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?

States a specific verb and resource ("Measure geometry in millimetres") and enumerates exactly what is produced: volume, surface area, centre of mass, bounding box, diagonal, and face/edge/vertex counts. The agent can tell this is the aggregate-measurement tool rather than a single-purpose one like bounding_box, though no sibling is named explicitly.

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 only implied by the tool's nature: measure when you need geometric metrics for a model. There is no statement of when to prefer this over bounding_box or inspect_document, no mention of prerequisites (open/active document), and no exclusions. The only concrete guidance is the instruction to pass objects to restrict scope.

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