Skip to main content
Glama
inventor-mcp-server

inventor-mcp-server

measure_distance

Read-only

Measure the minimum distance in millimeters between two assembly occurrences, including parts in sub-assemblies, to check for touching or overlapping components.

Instructions

Minimum distance in mm between two occurrences (0 = touching/overlapping). Names as in manage_occurrences; "Asm:1/2" reaches a part inside a sub-assembly.

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

Input Schema

NameRequiredDescriptionDefault
aYes
bYes
instanceNoWhich connected Inventor to use (list_instances). Leave empty when only one is connected.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.8.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description goes beyond that by disclosing the unit of measure and how to interpret a zero result, and by explaining the sub-assembly path syntax — real behavioral value not present in the structured fields.

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?

Two compact sentences, with the core measurement semantics front-loaded and the addressing convention second. Nothing is redundant and no sentence is filler.

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?

For a read-only two-argument measurement tool with an output schema already present, the description supplies units, result interpretation, and argument addressing rules. Only edge-case behavior (e.g., what happens when a name does not resolve) is left unstated, which is a minor gap.

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 description coverage is only 33%: 'a' and 'b' are bare strings and only 'instance' is documented. The description compensates well by specifying that both names follow manage_occurrences conventions and by explaining the 'Asm:1/2' sub-assembly addressing form, which is exactly the syntax an agent needs to form valid arguments.

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 description states a specific verb and resource (measure the minimum distance between two occurrences), gives the unit (mm), and defines the degenerate case (0 = touching/overlapping). An agent can distinguish this from mutation siblings like manage_occurrences, though it does not explicitly contrast with the adjacent check_interference tool.

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 implied by the tool name and the note that arguments use names 'as in manage_occurrences', which usefully routes the agent to a sibling for sourcing identifiers. However, there is no explicit statement of when to prefer this tool over interference/clearance checks, and no prerequisites or failure guidance.

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