Skip to main content
Glama
solidworks-mcp

solidworks-mcp

add_mate

Adds coincident, concentric, parallel, perpendicular, tangent, distance, or angle mates between two assembly components using points or entity names, then moves components to satisfy the constraint.

Instructions

Adds a geometric mate constraint between two components in the active assembly.

Specify entities either by 3D points [x, y, z] mm in assembly coordinates lying on the faces/edges, or by entity names (e.g. 'Plane1@Part1-1@Assembly1'). Supported mate types: coincident, concentric, parallel, perpendicular, tangent, distance, angle. The components move to satisfy the mate. Replaces the current selection.

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": {
      "mate_type": "<mate_type>"
    },
    "name": "add_mate"
  }
}

Input Schema

NameRequiredDescriptionDefault
flipNo
alignmentNoclosest
angle_degNoAngle in degrees for angle mate
mate_typeYes
distance_mmNoDistance in mm for distance mate
entity1_nameNo
entity2_nameNo
entity1_pointNo
entity2_pointNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare this as a non-readonly, non-idempotent mutation, and the description adds real side-effect context beyond them: 'The components move to satisfy the mate' and 'Replaces the current selection.' It doesn't mention failure modes such as over-constrained or conflicting mates, which keeps it from a 5.

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?

Front-loaded with the core action, then entity specification, then supported types, then side effects. Five short sentences, none redundant, each adding a distinct fact.

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 mutation tool with annotations and an output schema, the description covers the essentials: what it creates, how to address entities, valid mate types, and that selection is replaced. Preconditions and conflict handling remain unstated, but return-value explanation is correctly omitted.

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?

With only 22% schema description coverage across 9 params, the description does meaningful compensating work: it defines the point format as [x, y, z] in mm in assembly coordinates lying on faces/edges, gives the entity-name syntax 'Plane1@Part1-1@Assembly1', and mirrors the mate_type enum. It leaves flip, alignment, and the mate_type-to-distance/angle coupling unexplained.

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: 'Adds a geometric mate constraint between two components in the active assembly.' The domain is unambiguous and implicitly separable from siblings like add_sketch_relation or add_sketch_dimension, though it never names a sibling to contrast with.

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?

Gives useful procedural guidance on how to identify entities (3D points vs. entity names, with a name syntax example) and enumerates the supported mate types, but never says when to choose this tool over related ones or what preconditions must hold (e.g., an active assembly with two components).

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