Skip to main content
Glama
FullyDefined – AI for SOLIDWORKS

FullyDefined – AI for SOLIDWORKS

draw_circle

Adds a circle to an open SOLIDWORKS sketch from center X/Y and radius, with optional units, enabling precise sketch geometry for part design.

Instructions

Add a circle to the open sketch, given its centre (x, y) and radius. In a part its diameter becomes a dimension when the sketch is closed, unless set first.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "x": "<x>",
      "y": "<y>",
      "radius": "<radius>"
    },
    "name": "draw_circle"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYesX of the centre
yYesY of the centre
unitNomm, cm, m, inch or ft
radiusYesCircle radius

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose one genuinely non-obvious trait — in a part the diameter becomes a dimension on sketch close unless set first — but omits error conditions (no active sketch), whether the new entity becomes selected, and any return identity for the created circle.

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?

Two compact sentences, front-loaded with the action and target before the secondary dimension behavior. The closing clause ("unless set first") is slightly terse and could be ambiguous, but nothing is wasted.

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 four-parameter geometry-creation tool with no output schema and no annotations, the definition covers the core action, the container, and one subtle downstream effect. The remaining gaps — failure mode with no open sketch and the unit parameter's semantics — are real but modest given the schema's complete coverage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents x, y, radius and the unit enum, and the description merely restates centre and radius. It adds no meaning about the unit parameter (whether it applies to radius only, or is inferred) beyond what the schema provides, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Add a circle") plus the target container ("the open sketch") and the defining inputs. It is clearly distinct from draw_arc and draw_rectangle on the sibling list, though it never names an alternative explicitly.

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 phrase "the open sketch" implies a precondition (a sketch must be active), but it never states that as a requirement or says what happens if none is open. There is no explicit when-to-use versus when-to-use-a-sibling guidance, and the unit parameter's role in choosing values is left implicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools