Skip to main content
Glama
FreeCAD Tutor MCP
by alex-r-t

measure_distance

Read-onlyIdempotent

Calculates the minimum 3D distance and delta vector between two objects or selected face, edge, or vertex references in a FreeCAD model.

Instructions

Measure minimum 3D distance and delta vector between two objects or Face/Edge/Vertex refs.

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": {
      "object1": "<object1>"
    },
    "name": "measure_distance"
  }
}

Input Schema

NameRequiredDescriptionDefault
object1Yes
object2No
doc_nameNo
subelement1No
subelement2No

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds that the result is a minimum distance and a delta vector, which is real behavioral content. It omits units, coordinate frame, and failure behavior (e.g., non-intersecting or empty selections), which would have raised the score.

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?

A single front-loaded sentence with no filler; the verb, the computed quantities, and the accepted input kinds all appear immediately. Nothing could be removed without losing information.

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

Completeness2/5

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

With five parameters at 0% schema coverage and an output schema that does cover the return shape, the description's job is chiefly to disambiguate inputs — which it fails to do for doc_name and the optional second object. An agent could call it, but only by guessing at the parameter contract.

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 all five parameters (object1, object2, doc_name, subelement1, subelement2) rest on bare titles. The description hints at a 'ref' pattern that likely maps to subelement1/subelement2, but it never explains doc_name, the default-empty object2, or how a subelement qualifies an object reference.

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 (measure) and the exact quantities returned: minimum 3D distance plus a delta vector. It also names the accepted reference types (objects or Face/Edge/Vertex refs), which is more precise than most siblings. It does not explicitly contrast itself with analyze_shape or find_faces, so it stops short of a 5.

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 guidance on when to choose this over analyze_shape or the find_* tools, and no prerequisites or exclusions. Critically, it does not explain what happens when object2 is omitted even though only object1 is required, leaving the single-input case ambiguous.

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