Skip to main content
Glama
Sign In
CDT AutoCAD Provider

CDT AutoCAD Provider

by SlncTrZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

dimension_linear

Creates linear dimensions from WCS extension points and a dimension-line point, with rotation in degrees; use for orthogonal 0°/90° placements, not angled geometry.

Instructions

Create a linear dimension from WCS extension points and dimension-line point; rotation is degrees and placement uses drawing units.

Side-effects: Adds linear DIMENSION entity. Disambiguation: Use for orthogonal (0 or 90 deg) dimensions; for angled geometry use dimension_aligned.

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": {
      "x1": "<x1>",
      "y1": "<y1>",
      "x2": "<x2>",
      "y2": "<y2>",
      "dim_x": "<dim_x>",
      "dim_y": "<dim_y>"
    },
    "name": "dimension_linear"
  }
}

Input Schema

NameRequiredDescriptionDefault
x1YesFirst extension line origin X coordinate in WCS
x2YesSecond extension line origin X coordinate in WCS
y1YesFirst extension line origin Y coordinate in WCS
y2YesSecond extension line origin Y coordinate in WCS
dim_xYesDimension line definition point X coordinate in WCS
dim_yYesDimension line definition point Y coordinate in WCS
layerNoTarget layer name. Uses active layer if omitted
rotationNoDimension line angle in degrees (0 for horizontal, 90 for vertical)

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv0.1.1
    • addedInput schema / properties / dim_x / description
      Added value: +"Dimension line definition point X coordinate in WCS"
    • addedInput schema / properties / dim_y / description
      Added value: +"Dimension line definition point Y coordinate in WCS"
    • addedInput schema / properties / layer / description
      Added value: +"Target layer name. Uses active layer if omitted"
    • addedInput schema / properties / rotation / description
      Added value: +"Dimension line angle in degrees (0 for horizontal, 90 for vertical)"
    • addedInput schema / properties / x1 / description
      Added value: +"First extension line origin X coordinate in WCS"
    • addedInput schema / properties / x2 / description
      Added value: +"Second extension line origin X coordinate in WCS"
    • addedInput schema / properties / y1 / description
      Added value: +"First extension line origin Y coordinate in WCS"
    • addedInput schema / properties / y2 / description
      Added value: +"Second extension line origin Y coordinate in WCS"
  2. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations only give readOnlyHint=false, so the description correctly discloses the mutation side-effect ('Adds linear DIMENSION entity'), which is the key context an agent needs before committing a write. It also clarifies unit conventions (degrees for rotation, drawing units for placement). It does not cover layer-targeting behavior or whether the new entity is returned/selected, so it stops short of full transparency.

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 sentences: purpose, side-effects, disambiguation. The single most decision-relevant fact (this is a write that creates an entity) and the routing rule are both front-loaded with zero filler.

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?

An output schema exists, so return-shape explanation is unnecessary, and annotations plus the side-effects line cover the safety profile. For an 8-parameter creation tool the description supplies the disambiguation and unit semantics an agent needs; minor gaps (layer fallback behavior, what the created handle looks like in practice) are already handled by schema defaults.

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 every parameter is already documented in structured form and the baseline is 3. The description reinforces meaning (WCS coordinates, degrees for rotation, drawing units for placement) but adds no syntax, constraints, or defaults beyond what the schema already states.

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 ('Create a linear dimension') and immediately identifies the geometric inputs (WCS extension points and dimension-line point) plus the rotation/placement conventions. Combined with the explicit disambiguation line, an agent can distinguish it from dimension_aligned, dimension_ordinate, etc. without reading schemas.

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?

The Disambiguation line explicitly states when to use this tool (orthogonal 0/90 deg dimensions) and names the sibling to use instead for angled geometry (dimension_aligned). That is exactly the when/when-not/alternative pattern.

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