Skip to main content
Glama
FullyDefined – AI for SOLIDWORKS

FullyDefined – AI for SOLIDWORKS

suppress_mate

Suppress a named mate so its joined components can move freely. Use it to release assembly motion without deleting the mate, then confirm the read-back state.

Instructions

Suppress a mate: it stays listed but holds nothing, so the components it joined can move. Reports the state read back.

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

Input Schema

NameRequiredDescriptionDefault
nameYesMate name from list_mates

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the non-obvious semantic that the mate is retained rather than removed, that suppression frees the joined components, and that it reports the state read back. It omits persistence/reversibility details (implied only by the unsuppress sibling) and error behavior for an unknown mate name.

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 with zero waste; the core effect is front-loaded and the reporting behavior closes it out. Every clause earns its place.

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 one-parameter mutation tool with no output schema, the description covers the state change and mentions that state is reported back. Only minor operational details — what happens on an invalid name or whether suppression persists across sessions — are absent.

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 coverage is 100% and the single parameter already documents itself as a 'Mate name from list_mates'. The description adds no format, casing, or sourcing detail beyond the schema, so the baseline 3 applies.

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 ('Suppress a mate') and immediately explains the resulting state: the mate stays listed but holds nothing, freeing the components it joined. That effect distinguishes it from unsuppress_mate and delete_mate without needing to name them, though no sibling is explicitly referenced.

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 the stated effect — you suppress a mate when you want joined components to move — but the description gives no explicit when-to-use framing, no prerequisites (e.g., mate must exist and come from list_mates), and no comparison to alternatives like edit_mate or delete_mate.

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