Skip to main content
Glama
FullyDefined – AI for SOLIDWORKS

FullyDefined – AI for SOLIDWORKS

delete_mate

Deletes a named mate from a SOLIDWORKS assembly and reports the mates that remain. Use it to remove a specific mate by name obtained from list_mates.

Instructions

Delete a mate by name (delete_feature also finds mates). Reports the mates that remain.

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

Input Schema

NameRequiredDescriptionDefault
nameYesMate name from list_mates

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose post-call behavior ("Reports the mates that remain"), which is useful return context, but it says nothing about permanence/undo, what happens to the constrained components, or failure modes when the name is wrong for a destructive operation.

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, zero filler, with the action and its disambiguation front-loaded before the return behavior.

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 tool with no output schema, the description covers what it does, how it differs from the nearest sibling, and what it returns. The remaining gap is destructive-operation caveats, which matter more here because no annotations declare the safety profile.

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 schema already says the value is a "Mate name from list_mates"; the description's "by name" adds nothing further. Baseline 3 applies since the schema does the heavy lifting.

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 ("Delete a mate") plus the scoping condition ("by name"), and explicitly separates itself from the delete_feature sibling. An agent can pick it out of the large delete_* family without inspecting any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The parenthetical "delete_feature also finds mates" names the alternative and hints at the condition that selects it, which is real routing guidance. It stops short of explicit when-not-to-use or preconditions (e.g., whether the mate must exist or be unsuppressed first).

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