Skip to main content
Glama
Sign In
CDT AutoCAD Provider

CDT AutoCAD Provider

by SlncTrZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

object_copy

Duplicate a CAD entity by a WCS dx/dy/dz offset in drawing units, creating a new entity at the shifted location and returning its identifier without deleting the source.

Instructions

Copy one object by WCS delta dx/dy/dz using drawing units and return the new entity identifier without deleting the source.

Side-effects: Creates a duplicate entity at the offset location. Disambiguation: Creates new object; use object_move to translate without duplication.

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_copy"
  }
}

Input Schema

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

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 offset in drawing units"
    • addedInput schema / properties / dy / description
      Added value: +"WCS delta Y offset in drawing units"
    • addedInput schema / properties / dz / description
      Added value: +"WCS delta Z offset in drawing units (default: 0.0)"
    • addedInput schema / properties / object_id / description
      Added value: +"Backend entity identifier or persistent CAD handle of object to copy"
  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 state readOnlyHint=false, so the description carries most of the behavioral explanation. It discloses the key side effect — creates a duplicate entity at the offset location — and clarifies that the source is not deleted. It does not discuss permissions or undo/transaction behavior, but the core mutation semantics are clear.

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 front-loaded with the main action and return behavior, followed by brief side-effect and disambiguation notes. Every sentence adds useful information with no filler.

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?

The tool has an output schema, so the description need not explain return structure. It still notes that the new entity identifier is returned, and it covers the essential mutation and disambiguation details for correct invocation.

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 dx, dy, dz, and object_id are already documented in the input schema. The description reiterates WCS delta and drawing units but does not add syntax or constraints beyond the schema, making the baseline 3 appropriate.

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: copy one object via WCS delta dx/dy/dz. It also states the return value and that the source is not deleted, and it distinguishes the operation from object_move.

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 names the alternative behavior: use object_move to translate without duplication. This gives the agent a clear rule for choosing between copying and moving.

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