Skip to main content
Glama
nx-ai-bridge

nx-ai-bridge

by qiuyekai

sketch_circle

Adds a full circle to a specified sketch using a center point and radius in millimeters.

Instructions

Add a full circle to a sketch.

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>"
    },
    "name": "sketch_circle"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/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, and it says nothing about the fact that this mutates model state, whether the sketch must exist or be open for edit, or where the resulting circle entity lands. It does not contradict anything, but for an unannotated write operation it discloses almost nothing.

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?

A single front-loaded sentence with zero wasted words. Its brevity is efficient rather than padded, though the same word count could have carried a prerequisite clause at no cost.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With only three fully documented parameters and no output schema, the description is nearly sufficient for correct invocation. What is missing is whether the call returns the created entity and whether the sketch argument must reference an existing, editable sketch.

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 coverage is 100%, with center coordinates, mm units, and an exclusive minimum on radius all documented in the schema. The description adds no meaning beyond that, so the baseline of 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?

The description uses a specific verb and resource ("Add a full circle"), and the word "full" signals the distinction from the sibling sketch_arc without naming it. It is clear on its own, though it never explicitly routes the agent away from the arc or rectangle siblings.

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 guidance on when to use this versus sketch_arc or the other sketch primitives, and no prerequisites are stated (e.g. that the named sketch must already exist and be active). The agent must infer everything from the name.

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