Skip to main content
Glama
Sign In
MCP_CAD

MCP_CAD

by danielproxd2
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

add_concentric_mate

Aligns axes of two cylindrical or conical entities by adding a concentric mate in SOLIDWORKS assemblies. Use for typical autoparts tasks like aligning bolt and sleeve.

Instructions

Mate concéntrico — alinea ejes de dos entidades cilíndricas/cónicas.

Uso típico autopartes: alineación de ejes de barrenos (perno + bocina, bocina + flecha, dos cojinetes en una caja). [en: Add a concentric mate between two cylindrical / conical entities — typical autoparts use is aligning bolt+sleeve, sleeve+shaft, or two bearings in a housing.]

Args: component1_name, component2_name: SW component instance names from get_active_assembly_info (e.g. "bracket_L-1"). entity1_id, entity2_id: SW entity name strings, e.g. "Face@bracket_L-1@assy" (locale-sensitive — copy verbatim from the assembly info response). align: "ALIGNED" or "ANTIALIGNED".

Returns the created mate's metadata.

Related: add_mate_by_face_position (no-entity-name convenience for box-style components), stack_components (3 mates in one call for a fully-constrained stacked pair).

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": {
      "component1_name": "<component1_name>",
      "entity1_id": "<entity1_id>",
      "component2_name": "<component2_name>",
      "entity2_id": "<entity2_id>"
    },
    "name": "add_concentric_mate"
  }
}

Input Schema

NameRequiredDescriptionDefault
alignNoALIGNED
entity1_idYes
entity2_idYes
component1_nameYes
component2_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.1

TDQS

A4.5/5.0
Behavior3/5

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

No annotations are provided, so the description must carry the behavioral disclosure burden. It states the tool returns created mate's metadata, but omits details on permissions, side effects (e.g., modification of assembly), or state dependencies. However, for a straightforward mate creation, the basic behavior is implied, earning a mid-range score.

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 well-structured with a summary, typical use, argument details, return info, and related tools. It is slightly long but efficiently front-loaded with the purpose. Every sentence contributes value, though minor redundancy exists (bilingual repetition could be streamlined).

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?

Given the tool's complexity (5 parameters, no output schema, 0% schema coverage), the description thoroughly covers all aspects: purpose, parameter meanings, usage context, related tools, and return value. It is fully adequate for correct invocation without requiring external resources.

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 description coverage is 0%, so the description is essential. It explains each parameter: component1_name and component2_name with examples ('bracket_L-1'), entity1_id and entity2_id with locale-sensitive string examples, and the align parameter with allowed values. This adds significant meaning beyond the bare 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 the tool's purpose: 'Mate concéntrico — alinea ejes de dos entidades cilíndricas/cónicas.' It uses a specific verb ('add concentric mate') and resource ('cylindrical/conical entities'), effectively distinguishing it from siblings like add_mate_by_face_position and stack_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?

The description provides typical use cases ('Uso típico autopartes: alineación de ejes de barrenos') and explicitly references related tools, explaining when to use alternatives ('add_mate_by_face_position for box-style components, stack_components for fully-constrained stacked pair'). This gives clear guidance on when to use this tool versus others.

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