Skip to main content
Glama
Sign In
CDT AutoCAD Provider

CDT AutoCAD Provider

by SlncTrZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

entity_create_circle

Creates a full 360-degree CIRCLE at a specified WCS center with a positive radius, optionally on a layer or color, and returns the new entity identifier.

Instructions

Create a CIRCLE at a WCS center with positive radius in drawing units, optionally on a layer/color, and return the new object identifier.

Side-effects: Adds CIRCLE entity to active space. Disambiguation: Use for full 360-degree circles; for circular segments use entity_create_arc.

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

Input Schema

NameRequiredDescriptionDefault
cxYesCenter X coordinate in WCS drawing units
cyYesCenter Y coordinate in WCS drawing units
colorNoAutoCAD Color Index (ACI 1-255). Uses ByLayer if omitted
layerNoTarget layer name. Uses active layer if omitted
radiusYesPositive circle radius in drawing units

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.1.1
    • addedInput schema / properties / color / description
      Added value: +"AutoCAD Color Index (ACI 1-255). Uses ByLayer if omitted"
    • addedInput schema / properties / cx / description
      Added value: +"Center X coordinate in WCS drawing units"
    • addedInput schema / properties / cy / description
      Added value: +"Center Y coordinate in WCS drawing units"
    • addedInput schema / properties / layer / description
      Added value: +"Target layer name. Uses active layer if omitted"
    • addedInput schema / properties / radius / description
      Added value: +"Positive circle radius in drawing units"
  2. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

The annotations only declare readOnlyHint=false, so the description usefully adds that the tool creates an entity in active space and returns the new object identifier. It does not discuss transaction requirements or permission constraints, but the side-effect is clearly disclosed.

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?

The description is short and front-loaded: core creation behavior first, then side-effects, then a clear disambiguation note. No sentence is wasted.

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?

An output schema exists, the input schema is fully documented, and the description covers the mutation side-effect and return identifier. For a create-entity tool, this is complete enough for an agent to select and invoke it correctly.

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 explains cx, cy, radius, layer, and color. The description repeats key constraints such as WCS units and positive radius but adds no significant parameter 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 uses a specific verb and resource: create a CIRCLE at a WCS center with positive radius. It also distinguishes this tool from the sibling entity_create_arc by scope.

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

Usage Guidelines5/5

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

It explicitly says when to use this tool (full 360-degree circles) and when to use the alternative (circular segments should use entity_create_arc). This is clear routing guidance.

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