Skip to main content
Glama
Sign In
CDT AutoCAD Provider

CDT AutoCAD Provider

by SlncTrZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

object_scale

Uniformly scales one CAD entity in the active drawing around a WCS base point by a positive factor; use it to resize geometry in place without repositioning.

Instructions

Scale one object uniformly about the supplied WCS base point by a positive factor; this mutates geometry in the active document.

Side-effects: Mutates entity scale in active drawing. Disambiguation: Modifies entity size; use object_move to reposition.

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

Input Schema

NameRequiredDescriptionDefault
base_xYesWCS X coordinate of scaling center base point
base_yYesWCS Y coordinate of scaling center base point
factorYesPositive uniform scaling multiplier (e.g. 2.0 = double size, 0.5 = half size)
object_idYesBackend entity identifier or persistent CAD handle of object to scale

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.1.1
    • addedInput schema / properties / base_x / description
      Added value: +"WCS X coordinate of scaling center base point"
    • addedInput schema / properties / base_y / description
      Added value: +"WCS Y coordinate of scaling center base point"
    • addedInput schema / properties / factor / description
      Added value: +"Positive uniform scaling multiplier (e.g. 2.0 = double size, 0.5 = half size)"
    • addedInput schema / properties / object_id / description
      Added value: +"Backend entity identifier or persistent CAD handle of object to scale"
  2. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

The description discloses the mutation up front ("mutates geometry in the active document") and repeats the specific side effect as entity scale, which is the level of detail annotations (readOnlyHint=false only) do not provide. It stops short of saying what happens to dependent geometry, whether the edit is undoable as a unit, or whether invalid factors are rejected.

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?

The purpose is front-loaded in a single well-formed sentence and the trailing lines are short and scannable. However, "mutates geometry in the active document" and "Side-effects: Mutates entity scale in active drawing" say essentially the same thing, which is mild 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 an output schema present and full parameter coverage, the description only needs to carry purpose, mutation risk, and sibling routing, all of which it does. Gaps are secondary: behavior for non-positive factors, dependency/undo implications, and whether block or xref entities are scalable are unaddressed.

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 positive-multiplier semantics and WCS base point. The description restates those same concepts (WCS base point, positive factor, uniform) without adding syntax or edge-case guidance, so 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 (scale), resource (one object), and the exact transform semantics (uniform, about a WCS base point, positive factor). The Disambiguation line explicitly distinguishes it from object_move, so an agent can separate it from siblings without opening the schema.

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?

The Disambiguation sentence names an alternative (object_move) and the condition that selects it (repositioning rather than resizing). It does not address other near-neighbors such as object_rotate or batch_transform_entities, so the guidance is clear 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