Skip to main content
Glama
FullyDefined – AI for SOLIDWORKS

FullyDefined – AI for SOLIDWORKS

draw_arc

Adds an arc to an open SOLIDWORKS sketch from centre, radius and start/end angles in degrees, drawn counter-clockwise. Use draw_circle instead when start and end angles are equal.

Instructions

Add an arc to the open sketch from its centre, radius and start / end angles (degrees), counter-clockwise from start to end. Equal angles are refused: use draw_circle for a full circle. In a part its radius 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": {
      "cx": "<cx>",
      "cy": "<cy>",
      "radius": "<radius>",
      "start_angle": "<start_angle>",
      "end_angle": "<end_angle>"
    },
    "name": "draw_arc"
  }
}

Input Schema

NameRequiredDescriptionDefault
cxYesX of the centre
cyYesY of the centre
unitNomm, cm, m, inch or ft
radiusYesArc radius
end_angleYesAngle where the arc ends, in degrees
start_angleYesAngle where the arc starts, in degrees

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the disclosure burden and does real work: it warns that equal start/end angles are rejected, specifies counter-clockwise sweep, and reveals a side effect most agents would not predict (the radius becomes a driving dimension in a part once the sketch closes unless already set). It does not say what the call returns or what happens on degenerate/invalid angle ranges beyond equality.

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?

Three short sentences, front-loaded with the core action and geometry, then the edge-case refusal, then the downstream consequence. Nothing is redundant and nothing could be cut without losing information.

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 an unannotated creation tool with no output schema, the description covers the prerequisite state, validation behavior, sweep convention, and a non-obvious model side effect. Remaining gaps are the return value and the unit default, which are modest given the otherwise dense coverage.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds genuine meaning beyond the field names: angles are in degrees and are interpreted counter-clockwise from start to end, which fixes the orientation convention an agent could otherwise get backwards. The optional unit parameter and its default are not addressed.

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 names a specific verb and resource ('Add an arc to the open sketch') and enumerates the defining geometry (centre, radius, start/end angles) plus the sweep direction. It explicitly distinguishes itself from the sibling draw_circle for the full-circle case, so an agent can select it without opening the schema.

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?

It states the operating context ('the open sketch') and routes the degenerate case to an alternative: 'Equal angles are refused: use draw_circle for a full circle.' That is an explicit when-not and alternative pairing, but there is no broader guidance on arc vs. polyline/line for other curve needs.

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