Skip to main content
Glama
danielproxd2

MCP_CAD

by danielproxd2

create_slot

Draws a straight slot on the active sketch using center-line endpoints and width, for adjustable bolt slots in stamped brackets.

Instructions

Draw a straight slot on the active sketch.

The slot is a rounded-rectangle: a rectangle of (length × width_mm) with semicircular end-caps. The center line runs from (x1, y1) to (x2, y2); width_mm is the slot's narrow dimension.

Args: x1_mm, y1_mm: One endpoint of the center line. x2_mm, y2_mm: The other endpoint. width_mm: Slot width (diameter of the round end-caps).

Common autoparts use: adjustable bolt slots in stamped brackets, typically 1× thru 2× the bolt clearance diameter for ±tolerance.

Caveat: requires an active sketch.

Caveat (paramétrico): el croquis NO es paramétrico. modify_dimension NO puede redimensionar el ancho ni mover los endpoints post-hoc — solo la profundidad de extrusión es paramétrica. Para cambiar la ranura, reconstruye desde una pieza nueva. [en: Sketch geometry has NO driving dimension — modify_dimension cannot resize the slot width or move endpoints post-hoc; only extrude depth is parametric. To resize, rebuild from a fresh part.]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
x1_mmYes
x2_mmYes
y1_mmYes
y2_mmYes
width_mmYes
Behavior4/5

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

Without annotations, the description discloses key behavioral traits: the sketch geometry is not parametric, modify_dimension cannot resize slot width or move endpoints, and rebuilding from a fresh part is required for changes. This provides good transparency beyond the schema.

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 clear opening sentence, bullet-style parameter explanations, and separate caveats. The bilingual section adds useful context but could be trimmed slightly; overall, every sentence adds value.

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 tool with 5 required parameters, no annotations, and no output schema, the description covers shape definition, parameter roles, usage caveats, and a common use case. It lacks explicit output specification but is otherwise thorough.

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?

All five parameters are explained in the description: endpoints (x1_mm,y1_mm and x2_mm,y2_mm) and width (width_mm) as slot width. The shape semantics are clarified (semicircular end-caps). Given 0% schema description coverage, this compensates effectively.

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 draws a straight slot on the active sketch, describes its geometry, and distinguishes it from sibling tools like create_line or create_rectangle by specifying the slot's rounded-rectangle shape and intended use.

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?

The description mentions a common use case (adjustable bolt slots) and a prerequisite (requires active sketch), but does not explicitly guide when to use this tool over alternatives or when not to use it.

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/solidworks-mcp'

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