Skip to main content
Glama
FullyDefined – AI for SOLIDWORKS

FullyDefined – AI for SOLIDWORKS

unsuppress_mate

Reactivates a suppressed mate and rebuilds the assembly, reporting the resulting state, moved components, and any mates that now have errors.

Instructions

Turn a suppressed mate back on and rebuild. Reports the state read back, which components moved, and any mates that now have errors.

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

Input Schema

NameRequiredDescriptionDefault
nameYesMate name from list_mates

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden, and it does disclose real side effects: a rebuild is triggered, components can move, and other mates may acquire errors. That is meaningful behavior beyond the name, but it omits permissions, whether the rebuild is undoable, and what happens if the mate cannot be resolved.

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 tight sentences: the action is front-loaded and the second sentence is devoted entirely to the return information. No filler or redundant restatement of the title.

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?

There is no output schema, and the description compensates by enumerating what is reported back: the read-back state, which components moved, and any newly errored mates. Combined with the disclosed rebuild side effect, this covers what an agent needs to call and interpret the tool, with only permission and failure-mode details missing.

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% and the single parameter is already documented as 'Mate name from list_mates'. The description adds no further semantics such as whether the name must match exactly or how ambiguity is resolved, so the schema does all the work.

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 uses a specific verb-plus-resource ('Turn a suppressed mate back on and rebuild') that makes the inverse relationship with the sibling suppress_mate immediately legible. It is clear what the tool does, though it never names the sibling explicitly, so differentiation relies on the agent reading 'unsuppress' against 'suppress'.

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 only implied: the agent must infer that this applies to mates that are currently suppressed and that suppress_mate is the counterpart. There is no explicit when-to-use or when-not-to-use statement and no prerequisite (e.g. document must be open) called out.

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