Skip to main content
Glama

set_mate_suppression

Suppress or resume a mate by name to temporarily park incorrect mates before recreating them or to clean up after component suppression.

Instructions

Suprimir o resolver un mate por nombre.

Casos de uso: desactivar un mate de rama incorrecta antes de recrearlo con place_and_mate (la receta pose→mate), y limpiar tras supresión de componentes. Nota (verificado en vivo 2026-06): en esta versión de SW, suprimir un componente NO marcó sus mates como suprimidos en la enumeración — el snapshot-diff de abajo es barato y cubre versiones donde sí cascada. [en: Suppress or resume a mate by name. Uses: park a wrong-branch mate before recreating it via place_and_mate, and post-component-suppression cleanup. Live note: on this SW version component suppression did NOT flip its mates' suppressed flags; the snapshot-diff below is cheap and covers versions where the cascade does happen.]

Workflow for cascade-aware resume: 1. Snapshot mates BEFORE suppressing the component: before = {m["name"] for m in get_active_assembly_info()["mates"] if m["suppressed"]} 2. Suppress the component, do your work, then resume it. 3. Snapshot mates AFTER: after = {m["name"] for m in get_active_assembly_info()["mates"] if m["suppressed"]} 4. The orphans are after - before. For each, call set_mate_suppression(mate_name, suppressed=False) to restore.

Args: mate_name: SW-assigned mate name from get_active_assembly_info, e.g. "Coincidente7". suppressed: True to suppress, False to resume (resolve).

Returns the mate's metadata with the new suppressed state.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
mate_nameYes
suppressedYes
Behavior5/5

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

With no annotations, the description carries full burden. It discloses that the tool suppresses/resumes a mate, returns metadata, and includes a live note about a version-specific lack of cascade, plus a cheap snapshot-diff workaround. This is excellent transparency.

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 moderately long but well-structured: purpose, use cases, workflow, parameter explanations. Each part earns its place, though could be slightly more concise. Still highly effective.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has 2 required params, both fully explained. No output schema but description states return value. Workflow adds depth for complex use cases. No gaps for a CAD suppression tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% and no param descriptions in schema. The description's 'Args' section explains mate_name (source and example) and suppressed (meaning of boolean). This adds significant meaning beyond the raw schema.

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 clearly states 'Suppress or resume a mate by name', using a specific verb and resource. It distinguishes from sibling tools like add_coincident_mate (which add mates) and set_components_suppression (which suppresses components).

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

Usage Guidelines5/5

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

Provides explicit use cases: disabling a wrong-branch mate before recreating via place_and_mate, and post-component-suppression cleanup. Includes a detailed workflow for cascade-aware resume, giving clear when-to-use context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/danielproxd2/MCP_CAD'

If you have feedback or need assistance with the MCP directory API, please join our Discord server