Skip to main content
Glama
FullyDefined – AI for SOLIDWORKS

FullyDefined – AI for SOLIDWORKS

list_mates

Lists every mate in the active SOLIDWORKS assembly, including type, value, involved components and geometry, alignment, suppression, flip state, limit range, and rebuild errors; read-only.

Instructions

List every mate of the active assembly: name, type, value (distance or angle), the two components, what was picked on each (plane, cylinder, point, line), alignment, whether the dimension is flipped, whether it is suppressed, and its error state after the last rebuild. A limit mate has type limit_distance with its minimum and maximum. Read-only.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_mates"
  }
}

Input Schema

NameRequiredDescriptionDefault
unitNoUnit for distances (mm, cm, m, inch or ft)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description must carry the behavioral load, and it does: it declares "Read-only" and discloses return-time facts beyond the schema, including that error state reflects the last rebuild and that limit mates surface as type limit_distance with min/max. It stops short of noting anything about scope (all mates vs. filtered) or cost, but the safety profile is clearly stated rather than left to inference.

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?

One front-loaded sentence declaring the operation and scope, followed by a compact enumeration of return fields, closed by the read-only flag. Every clause carries information; there is no filler and the safety note is placed where it will be read.

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?

Since there is no output schema, the description's field enumeration is the only description of return shape, and it covers it thoroughly, including edge cases like limit mates and post-rebuild error states. The remaining gap is minor: no statement about ordering, volume, or whether an empty result is possible.

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?

The single parameter `unit` has full schema coverage (100%) including its own description and allowed values, so the schema does the work. The description never mentions unit at all, so it adds no meaning beyond it — baseline 3 is appropriate given the schema's completeness.

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?

States a specific verb and resource ("List every mate of the active assembly") and then enumerates exactly what each mate record contains — name, type, value, components, selection geometry, alignment, flip/suppress flags, error state. This is precise enough to distinguish it from sibling listers like list_dimensions or list_features without consulting a schema.

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 "of the active assembly" — the agent infers an assembly must be active — but there is no explicit when-to-use, no mention of prerequisites (e.g., document must be an assembly, not a part), and no routing to alternatives such as list_dimensions. Guidance exists only by implication.

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