Skip to main content
Glama

Interface Align Check

interface_align_check
Read-only

Verify secondary interface pairs coincide in world space after the primary mate seats a part, returning misaligned pairs with gap distances beyond the tolerance.

Instructions

Gate: verify declared interface pairs coincide in world space — the "do the OTHER interfaces line up?" check for multi-interface mates. After the primary mate seats a part, this confirms its secondary interfaces (a second bolt pattern, a bore axis) actually meet the parent's.

pairs: [{child, child_iface, parent, parent_iface}, ...] (child/parent are link names in the assembly). Returns misaligned pairs [{..., gap_mm}], empty if every pair coincides within tol_mm.

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": {
      "assembly": "<assembly>",
      "pairs": "<pairs>"
    },
    "name": "interface_align_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
pairsYes
tol_mmNo
assemblyYes
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

A3.8/5.0
Behavior3/5

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

readOnlyHint=true already declares this is a non-mutating check, so the description isn't carrying the safety burden. It does add useful behavior beyond annotations: it returns misaligned pairs with gap_mm and an empty list when everything is within tol_mm, which matters since there is no output schema. It stops short of describing permissions or failure behavior (e.g., what happens for unknown link/interface names).

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 'Gate:' role, then the distinguishing gloss, then the parameter and return semantics. The nested-quote framing and em-dash clause are slightly dense but each sentence adds information an agent needs.

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 4-parameter read-only check with 25% schema coverage and no output schema, the description supplies the pair structure and the return contract, which is the bulk of what an agent needs. Missing only edge-case behavior and explicit assembly semantics.

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 25% (only workspace is documented), so the description must compensate — and largely does, spelling out the pairs item shape as {child, child_iface, parent, parent_iface}, clarifying child/parent are assembly link names, and tying tol_mm to the coincidence threshold. assembly itself is left implicit.

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 (verify declared interface pairs coincide in world space) and frames it as the 'do the OTHER interfaces line up?' gate for multi-interface mates. This distinguishes it conceptually from interference_check and component_contract_check, 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 Guidelines4/5

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

Gives a concrete triggering condition: run it after the primary mate has seated a part, to confirm secondary interfaces meet the parent's. That is clear usage context, but there are no explicit exclusions or named alternatives for the adjacent alignment/contract checks.

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