Skip to main content
Glama

create_circle

Draw a circle on the active sketch by specifying center coordinates and radius. Use for bolt holes, bearing bores, and fillet circles before extrusion or cutting.

Instructions

Draw a circle on the active sketch.

Args: cx_mm, cy_mm: Center point in mm (sketch-local frame). Long-form aliases center_x_mm / center_y_mm accepted (kwarg-only) for parity with the composite tools (add_bolt_circle, build_rectangular_pocket, etc.). Pass one name per axis, not both. radius_mm: Circle radius in mm. Must be positive.

Returns the circle's center and radius/diameter. Common autoparts use: bolt holes, bearing bores, fillet circles before extruding/cutting.

Example — 8.5 mm clearance hole at origin (M8 medium per ISO 273): create_circle(0, 0, 4.25) # or equivalently: create_circle(center_x_mm=0, center_y_mm=0, radius_mm=4.25)

Caveat: requires an active sketch.

Caveat (paramétrico): el croquis NO es paramétrico. modify_dimension NO puede redimensionar el diámetro ni mover el centro post-hoc — solo la profundidad de extrusión es paramétrica. Si el usuario pide "hazlo más grande" o "cámbialo a Ø10", reconstruye desde una pieza nueva. [en: Sketch geometry has NO driving dimension — modify_dimension cannot resize the OD or move the center post-hoc; only extrude depth is parametric. To resize ("make it bigger"), rebuild from a fresh part.]

Related: add_bolt_circle (one call for N holes on a bolt circle — use instead of N create_circle + extrude_cut sequences for typical flange / bracket bolt patterns).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cx_mmNo
cy_mmNo
radius_mmNo
center_x_mmNo
center_y_mmNo
Behavior5/5

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

With no annotations, the description fully discloses behavioral traits: requires an active sketch, the circle geometry is non-parametric (modify_dimension cannot resize), and rebuilding from a fresh part is needed for resizing. It also mentions return values, providing complete transparency.

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 main sentence, parameter details, example, and caveats. The bilingual caveat adds length but serves multilingual users. Overall efficient and front-loaded with the core purpose.

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 5 parameters, no annotations, no output schema, and low schema coverage, the description covers purpose, parameters, usage, behavioral traits, and alternatives comprehensively. The return value indication and example complete the context.

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?

The schema has 0% description coverage, but the description thoroughly explains each parameter: cx_mm/cy_mm as center point, radius_mm as radius with positivity constraint, and long-form aliases. It clarifies that only one name per axis should be passed, adding essential meaning beyond the schema.

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 circle on the active sketch with a specific verb and resource. It distinguishes from the sibling tool add_bolt_circle by suggesting the latter for multiple holes, enhancing clarity.

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?

The description provides clear context for usage, including an example, parameter constraints, and a recommendation to use add_bolt_circle for bolt patterns. However, it does not explicitly state when not to use the tool, but the context is sufficient.

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