Skip to main content
Glama

create_arc

Draw a center-defined arc on an active sketch by specifying center, radius, start/end angles, and direction for cw or ccw sweep.

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
Behavior5/5

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

With no annotations, the description fully explains behavior: angle convention, direction flag's counter-intuitive effect, return value, and caveat. No behavior is left unspecified.

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 with sections, though somewhat verbose. Every sentence adds value, but could be slightly trimmed. Still very effective.

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 no annotations, no output schema, and complex behavior, the description is fully complete—covers arguments, returns, use cases, examples, and prerequisites.

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 coverage is 0%, but the description compensates by detailing every parameter, including constraints (radius positive, angles different) and aliases. Examples illustrate usage.

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 center-defined arc on the active sketch, distinguishing it from siblings like create_circle and create_slot.

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?

It provides explicit when-to-use guidance (slot end-caps, fillets, profiles) and when-not-to (use create_circle for full circles). Also mentions prerequisite (active sketch via create_sketch).

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/MCP_CAD'

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