Skip to main content
Glama
FullyDefined – AI for SOLIDWORKS

FullyDefined – AI for SOLIDWORKS

edit_mate

Change a mate's distance, angle, limit, or alignment, rebuild the assembly, reject changes other mates block, and report the updated mate and moved components.

Instructions

Change an existing mate: value for a new distance or angle, flip_dimension to put the distance / angle on the other side, flip_alignment to swap aligned and anti-aligned (or alignment to set it directly). The assembly is rebuilt; a change the other mates do not allow is undone and refused. Reports the mate as read back and which components moved.

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

Input Schema

NameRequiredDescriptionDefault
nameYesMate name from list_mates, e.g. 'Distance1'
unitNoUnit of the distance (mm, cm, m, inch or ft)
valueNoNew distance (in unit) for a distance mate, or degrees for an angle mate
maximumNoNew largest distance of a limit distance mate
minimumNoNew smallest distance of a limit distance mate
alignmentNoSet the alignment outright instead of flipping it
flip_alignmentNoSwitch between aligned and anti-aligned
flip_dimensionNoPut the distance / angle on the other side

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?

No annotations are provided, so the description carries the full behavioral burden. It discloses important side effects: the assembly is rebuilt, invalid changes are undone and refused, and the result reports the mate as read back plus which components moved. It does not mention permissions or whether successful edits are reversible, so it falls short of 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences and front-loads the core action. The first sentence is dense with parenthetical alternatives, but every part earns its place and there is no 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 an 8-parameter mutation tool with no annotations and no output schema, the description covers the key behavioral context: rebuild behavior, refusal of invalid changes, and return information. It omits some parameter-level detail, but the schema already documents all parameters.

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?

Schema description coverage is 100%, so the baseline is 3. The description adds some meaning by explaining that value applies to distance or angle and by clarifying the interaction between flip_alignment and alignment, but it does not add much for unit, maximum, minimum, or name beyond what the schema already provides.

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 verb and resource: 'Change an existing mate.' It also lists the editable aspects (value, flip_dimension, flip_alignment, alignment), making clear this is an edit operation on an existing mate rather than creation or deletion.

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 'existing mate' and the editable fields, but there is no explicit guidance on when to use this versus add_mate, delete_mate, or other mate tools. No prerequisites or exclusions are stated.

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