Skip to main content
Glama
danielproxd2

MCP_CAD

by danielproxd2

create_arc

Draw a center-defined arc on the active sketch by specifying center, radius, start and end angles, and direction. Use for slot end-caps, 2D fillets, or curved handle profiles.

Instructions

Arco — draw a center-defined arc on the active sketch.

Center + radius + start/end angles. The angle convention is standard math: 0° points along the +X sketch axis, angles grow CCW. The direction flag picks which of the two possible arcs (the short or long way around) gets drawn between the two endpoints.

Args: cx_mm, cy_mm: Arc center in mm (sketch-local frame). Long-form aliases center_x_mm / center_y_mm accepted (kwarg-only) for parity with the composite tools. Pass one name per axis. radius_mm: Arc radius in mm. Must be positive. start_angle_deg: Start angle from the +X sketch axis. Standard math convention (CCW-positive). end_angle_deg: End angle, same convention. Must differ from start_angle_deg (use create_circle for full circles). direction: "ccw" (default) sweeps counter-clockwise from start to end; "cw" sweeps the other way around. Counter- intuitive: for the SAME start/end angles, "ccw" and "cw" produce arcs that sweep opposite ways. Quarter-arc from start=180° to end=90°: "cw" → 90° sweep (natural quarter), "ccw" → 270° sweep (the long way around). If a revolve_sketch after the arc fails, the arc landed on the wrong side — flip direction.

Returns dict with center, radius, angles, direction, computed start/end XY coords, signed sweep angle, and arc length.

Common autoparts use: - Slot end-cap when create_slot doesn't fit (e.g. one-ended slot with custom radius) - 2D fillet between two lines in a sketch (radius = corner fillet, start/end angles set by the line directions) - Curved scraper / handle profiles where the chevron+slant polygon would otherwise approximate

Example — quarter circle, R=10, from +X axis to +Y axis, CCW: create_arc(0, 0, 10, 0, 90) # or equivalently: create_arc(center_x_mm=0, center_y_mm=0, radius_mm=10, start_angle_deg=0, end_angle_deg=90)

Example — rounded slot end at the right side of a horizontal slot (180° arc spanning the slot width = 6mm at x=50): create_arc(50, 0, 3, -90, 90)

Caveat: requires an active sketch (call create_sketch or create_sketch_on_face first).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cx_mmNo
cy_mmNo
directionNoccw
radius_mmNo
center_x_mmNo
center_y_mmNo
end_angle_degNo
start_angle_degNo
Behavior4/5

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

No annotations provided, so description carries full burden. Explains angle convention (CCW), direction flag with counter-intuitive example, returns dict with fields, and troubleshooting tip (flip direction if revolve fails). Missing some error cases but overall transparent.

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?

Well-structured: purpose first, then parameters, returns, use cases, examples, caveat. Front-loaded and efficient, though slightly long. 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?

Given 8 parameters, no output schema, and no annotations, the description covers parameter conventions, examples, use cases, and a key caveat (active sketch needed). Does not cover all edge cases but is sufficient for typical use.

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 has 0% description coverage; the description explains all 8 parameters in detail: meanings, defaults, constraints (radius positive, start/end different), long-form aliases, and direction behavior. Fully compensates for schema gap.

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 'draw a center-defined arc on the active sketch' with specific parameters (center, radius, angles). It distinguishes from siblings like create_circle (full circles) and create_slot (slot end-caps).

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?

Provides clear context: requires active sketch, common use cases (slot end-cap, 2D fillet, curved profiles), and explicitly says to use create_circle for full circles. Lacks explicit when-not-to-use but gives good guidance.

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