Skip to main content
Glama
danielproxd2

MCP_CAD

by danielproxd2

create_rectangle

Creates a rectangle on an active sketch by specifying two opposite corner coordinates in millimeters. Requires a prior create_sketch call.

Instructions

Draw a corner-defined rectangle on the active sketch.

Args: x1_mm, y1_mm: One corner of the rectangle in mm (sketch-local). x2_mm, y2_mm: The opposite corner.

The rectangle is added to whatever sketch was started by the most recent create_sketch() call. Returns the rectangle's geometric properties (width and height in mm) for the LLM to verify.

Example — 50mm × 30mm rectangle starting at the origin: create_rectangle(0, 0, 50, 30)

Caveat: requires an active sketch (create_sketch first).

Caveat (paramétrico): el croquis NO es paramétrico. modify_dimension NO puede redimensionar el ancho/alto post-hoc — solo la profundidad de extrusión es paramétrica. Para cambiar el tamaño del rectángulo, reconstruye desde una pieza nueva. [en: Sketch geometry has NO driving dimension — modify_dimension cannot resize the rectangle post-hoc; only extrude depth is parametric. To resize, rebuild from a fresh part.]

Related: build_rectangular_pocket (sketch + cut in one call when the intent is a rectangular pocket — most common autoparts use of this primitive).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
x1_mmYes
x2_mmYes
y1_mmYes
y2_mmYes
Behavior5/5

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

Describes that rectangle is added to most recent sketch, returns geometric properties, and crucially warns that rectangle is not parametric (modify_dimension cannot resize; only extrude depth is parametric). No annotations provided, so description fully bears transparency.

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?

Well-structured with args, example, caveat, and related tool. Front-loaded purpose. No filler; every sentence adds value.

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?

Covers purpose, parameters, example, behavioral caveats (non-parametric), prerequisites, and sibling alternative. No output schema needed since return value is simple geometric properties. Complete for safe agent usage.

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?

Explains param meaning: 'One corner of the rectangle in mm' and 'The opposite corner.' Provides example (0,0,50,30) to clarify usage. Input schema has 0% description coverage, so description compensates fully.

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?

Clearly states 'Draw a corner-defined rectangle on the active sketch.' Distinguishes from sibling build_rectangular_pocket by noting it is sketch-only vs sketch+cut.

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?

Explicitly requires an active sketch ('create_sketch first'). Provides alternative build_rectangular_pocket for rectangular pockets, guiding when to use this primitive vs a combined operation.

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