Skip to main content
Glama
Sign In
CDT AutoCAD Provider

CDT AutoCAD Provider

by SlncTrZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

object_move

Moves a single object by WCS delta dx/dy/dz in drawing units, shifts its coordinates in the active drawing, and returns the normalized updated entity.

Instructions

Move one object by WCS delta dx/dy/dz using drawing units and return the normalized updated entity; this mutates geometry.

Side-effects: Shifts entity coordinates in active drawing. Disambiguation: Use for translation; use object_rotate or object_scale for other transforms.

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>",
      "dx": "<dx>",
      "dy": "<dy>"
    },
    "name": "object_move"
  }
}

Input Schema

NameRequiredDescriptionDefault
dxYesWCS delta X translation in drawing units
dyYesWCS delta Y translation in drawing units
dzNoWCS delta Z translation in drawing units (default: 0.0)
object_idYesBackend entity identifier or persistent CAD handle of object to move

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.1.1
    • addedInput schema / properties / dx / description
      Added value: +"WCS delta X translation in drawing units"
    • addedInput schema / properties / dy / description
      Added value: +"WCS delta Y translation in drawing units"
    • addedInput schema / properties / dz / description
      Added value: +"WCS delta Z translation in drawing units (default: 0.0)"
    • addedInput schema / properties / object_id / description
      Added value: +"Backend entity identifier or persistent CAD handle of object to move"
  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?

Annotations only supply readOnlyHint=false, so the description carries most of the burden and does well: it discloses that geometry is mutated, that entity coordinates shift in the active drawing, and that a normalized updated entity is returned. It doesn't mention undo/transaction interaction, which keeps it short of a 5.

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?

Front-loaded with the core action, then clearly labeled Side-effects and Disambiguation lines. Every sentence adds information without waste.

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 so return-format explanation isn't needed, all params are documented, and the mutation behavior is disclosed. Nothing required to invoke correctly is missing.

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% and each parameter is documented (including dz default of 0), so the schema already does the heavy lifting. The description adds only the framing of dx/dy/dz as WCS deltas in drawing units, meeting the baseline 3.

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 (move), resource (one object), and coordinate semantics (WCS delta dx/dy/dz in drawing units), plus the return value. It also names sibling transforms it is not, so an agent can distinguish it from object_rotate/object_scale.

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?

Explicit disambiguation: 'Use for translation; use object_rotate or object_scale for other transforms.' The mutation constraint is also stated, giving clear when-to-use and when-not 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