Skip to main content
Glama
maximedns5

freecad-mcp

by maximedns5

measure_gap

Measure the actual gap between two parts' bounding boxes along an axis to size and position a spanning part correctly, preventing overhangs from misalignment.

Instructions

Measure the real gap between two parts' bounding boxes along one axis.

Use this before building a part meant to span two others (e.g. a chair
stretcher between two legs): size and position the spanning part from
the measured gap, instead of deriving a span independently of where
those parts actually ended up — that mismatch is exactly how a
stretcher ends up overhanging its legs by tens of mm.

This is an axis-aligned bounding-box measurement (v0 of a joint model),
not a full face-to-face mate — it does not handle rotated parts or
non-axis-aligned relationships.

Args:
    doc_name: The name of the document.
    part_a: Name of the first part.
    part_b: Name of the second part.
    axis: Which axis to measure the gap along: "x", "y", or "z".

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
axisYes
part_aYes
part_bYes
doc_nameYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations, the description discloses key behavioral traits: it is a bounding-box approximation ('v0 of a joint model') and has limitations regarding rotation and non-axis-aligned cases. It does not mention return format or edge cases, but the output schema likely covers return structure.

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?

The description is well-structured and front-loaded: purpose first, then use case, then limitations. Every sentence adds value, and the length is appropriate for the tool's complexity.

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?

The description covers purpose, use case, and limitations, which is sufficient given the output schema exists. It lacks details like signed vs. absolute gap or overlapping parts behavior, but those are not critical for an initial measurement tool.

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 compensates by naming all parameters and explaining axis values ('x', 'y', 'z'). However, part_a, part_b, and doc_name only receive minimal restatement ('Name of the first part'), adding little beyond the schema's field titles.

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 opens with a specific verb+resource: 'Measure the real gap between two parts' bounding boxes along one axis.' It also clarifies it is an axis-aligned bounding-box measurement, not a face-to-face mate, distinguishing it from the sibling 'measure' tool.

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

Usage Guidelines5/5

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

It explicitly states when to use: 'Use this before building a part meant to span two others' and explains the reasoning. It also provides exclusions: 'does not handle rotated parts or non-axis-aligned relationships,' making the usage boundaries clear.

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/maximedns5/freecad-mcp'

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