Skip to main content
Glama
Sign In
CDT AutoCAD Provider

CDT AutoCAD Provider

by SlncTrZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

object_rotate

Rotate a single CAD entity counter-clockwise around a specified WCS base point by an angle in degrees, updating its geometry in the active drawing.

Instructions

Rotate one object around the supplied WCS base point by angle_deg in degrees; this mutates geometry in the active document.

Side-effects: Mutates entity geometry in active drawing. Disambiguation: Rotates geometry counter-clockwise in degrees; use object_scale to resize or object_move to translate.

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": {
      "object_id": "<object_id>",
      "base_x": "<base_x>",
      "base_y": "<base_y>",
      "angle_deg": "<angle_deg>"
    },
    "name": "object_rotate"
  }
}

Input Schema

NameRequiredDescriptionDefault
base_xYesWCS X coordinate of rotation center base point
base_yYesWCS Y coordinate of rotation center base point
angle_degYesRotation angle in degrees (counter-clockwise)
object_idYesBackend entity identifier or persistent CAD handle of object to rotate

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.1.1
    • addedInput schema / properties / angle_deg / description
      Added value: +"Rotation angle in degrees (counter-clockwise)"
    • addedInput schema / properties / base_x / description
      Added value: +"WCS X coordinate of rotation center base point"
    • addedInput schema / properties / base_y / description
      Added value: +"WCS Y coordinate of rotation center base point"
    • addedInput schema / properties / object_id / description
      Added value: +"Backend entity identifier or persistent CAD handle of object to rotate"
  2. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false; the description adds real context by stating the operation mutates entity geometry in the active drawing and specifying counter-clockwise degrees. It omits whether rotation is about the WCS Z-axis only and whether changes are undoable, which would complete the mutation profile.

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 labeled lines: the action and its inputs come first, followed by side-effects and disambiguation. Every sentence carries distinct information with no redundancy.

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?

With full schema coverage and an output schema present, the description needn't explain returns, and it covers mutation and direction adequately. Minor gaps remain around axis of rotation and undo/transaction expectations for a mutating call.

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 all four parameters are already documented, including the counter-clockwise convention and WCS base point. The description largely restates those facts rather than adding new semantics, so the baseline 3 applies.

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?

States a specific verb and resource ('Rotate one object') plus the exact governing parameters (WCS base point, angle_deg). The Disambiguation line explicitly contrasts it with object_scale and object_move, so an agent can select it without opening sibling schemas.

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?

Explicitly routes the agent to object_scale for resizing and object_move for translation, giving clear alternative selection criteria. It stops short of stating preconditions (e.g., entity must exist, or that a transaction/undo may be warranted), so it is strong but not exhaustive.

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