Skip to main content
Glama
Sign In
MCP_CAD

MCP_CAD

by danielproxd2
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

new_assembly

Creates a new empty assembly document and activates it in SolidWorks. Provides a starting point for inserting components and adding mates.

Instructions

Crear un ensamble nuevo y vacío (documento .SLDASM).

Abre y activa un ensamble en blanco desde la plantilla por defecto. Punto de partida para insertar componentes y mates. [en: Create + activate a new empty assembly — the starting point for inserting components and mates.]

Returns: {"name": str, "type": "assembly", "created": True}

Caveat: requiere SolidWorks abierto (NO lanza el proceso). [en: requires SW already running; does not launch it.]

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "new_assembly"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.1

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations, description fully discloses behavior: creates and activates empty assembly, requires SW already running, does not launch SW. Returns a dictionary with name and created status.

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?

Bilingual but concise, covering purpose, usage context, caveat, and return value in a few sentences. Information is well-structured and front-loaded.

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?

No parameters or output schema needed. Description completely covers essential information: what it does, return format, and prerequisite (SW running).

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

Parameters4/5

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

Tool has zero parameters; baseline score of 4 applies. Description does not need to add parameter info.

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?

Explicitly states it creates a new empty assembly (.SLDASM), activates it from default template, and is starting point for inserting components. Clearly distinguishes from sibling tools like new_part and open_document.

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?

Describes as starting point for components and mates, and includes caveat that SolidWorks must already be running. Provides clear context for when to use.

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