Skip to main content
Glama
nx-ai-bridge

nx-ai-bridge

by qiuyekai

sketch_arc

Adds a counter-clockwise circular arc to a named sketch from specified start and end angles in degrees, using a center point and radius to define the arc.

Instructions

Add a circular arc to a sketch, counter-clockwise from start_angle to end_angle (degrees, measured from the sketch x axis).

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": {
      "sketch": "<sketch>",
      "center": "<center>",
      "radius": "<radius>",
      "start_angle": "<start_angle>",
      "end_angle": "<end_angle>"
    },
    "name": "sketch_arc"
  }
}

Input Schema

NameRequiredDescriptionDefault
centerYesCentre [x, y] in sketch coordinates (mm)
radiusYesRadius (mm).
sketchYesSketch name.
end_angleYesEnd angle in degrees.
start_angleYesStart angle in degrees.

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?

With no annotations, the description carries the full burden, and it does disclose one genuinely useful behavioral trait: the arc is swept counter-clockwise and angles are measured from the sketch x axis, which resolves the ambiguity a bare 'start/end angle' would leave. It says nothing about preconditions (must the sketch exist?), failure modes, or what the tool returns, which matters for an unannotated mutation.

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?

A single sentence with the action front-loaded, followed by the geometric convention that disambiguates the angles. No filler or restatement of the tool name.

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 five-required-parameter geometry tool with no output schema and no annotations, the description covers the essential geometry and the angle convention. The main remaining gap is the precondition that the sketch must already exist and whether a failure is raised otherwise.

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 real meaning beyond the schema for start_angle and end_angle: the sweep direction and the reference axis, neither of which the schema states ('Start angle in degrees'). Center and radius semantics remain purely schema-driven.

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 circular arc to a sketch') plus the defining geometry, which lets an agent distinguish it from sketch_circle, sketch_line, and sketch_rectangle without opening a schema. It stops short of naming those siblings explicitly, so differentiation is inferred from the geometry rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no mention of alternatives (e.g. sketch_circle for a full circle), and no prerequisite stated such as the target sketch already existing. Usage is only implied by the phrase 'to a sketch'.

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