Skip to main content
Glama

Min Clearance

min_clearance
Read-only

Measure the minimum distance between two solids to determine clearance status: clear, contact, or interference. Returns gap size, contact points, and overlap volume for precise design validation.

Instructions

Closest approach between two solids — the measured gap, richer than the binary interference_check. a and b are object handles. All lengths mm, volumes mm³.

Returns a dict: status: "clear" (a positive gap separates them), "contact" (faces/edges touch, gap ~ 0), or "interference" (the solids interpenetrate / share material). clearance_mm: minimum distance between the two solids (mm). 0.0 when they are touching or interfering. overlap_volume_mm3: volume of interpenetration (mm³). Present ONLY when status == "interference". point_on_a: [x,y,z] of the closest point on a. Present when status is "clear" or "contact" (omitted for "interference"). point_on_b: [x,y,z] of the closest point on b. Present when status is "clear" or "contact" (omitted for "interference").

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": {
      "a": "<a>",
      "b": "<b>"
    },
    "name": "min_clearance"
  }
}

Input Schema

NameRequiredDescriptionDefault
aYes
bYes
workspaceNoRun this call in this named workspace

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.7
    • addedInput schema / properties / workspace
      Added value: +{
      +  "default": "",
      +  "description": "Run this call in this named workspace",
      +  "title": "Workspace",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the read-only annotation, the description richly discloses return behavior: the three status values, units, when `clearance_mm` is zero, when `overlap_volume_mm3` appears, and when `point_on_a`/`point_on_b` are omitted. This gives the agent the conditional output semantics needed to interpret results correctly.

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 front-loaded with the core purpose and sibling comparison, then uses a compact structured return-value block. Every element—units, status meanings, conditional fields—earns its place for a tool without an output schema.

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

Completeness5/5

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

With no output schema, the description fully documents the return dictionary, including conditional field presence and units. Combined with the read-only annotation and schema-covered required handles, an agent has everything needed to invoke and interpret the tool.

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

Parameters4/5

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

Schema coverage is only 33%, but the description compensates for the required parameters by explaining that `a` and `b` are object handles. It also states units globally. The `workspace` parameter is left to its schema description, which is sufficient.

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 states a specific measurement operation: the closest approach between two solids, returning the measured gap. It explicitly distinguishes itself from the sibling `interference_check` as richer than a binary check, and identifies `a` and `b` as object handles.

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

Usage Guidelines4/5

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

It clearly positions the tool relative to `interference_check` by saying it returns the measured gap rather than a binary result. However, it does not explicitly state preconditions such as both handles needing to reference solid bodies, nor does it enumerate when not to use it.

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

Deploy Server

Other Tools