Skip to main content
Glama
U-C4N

AutoCAD MCP Pro

by U-C4N
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Styles: Create Dimension Style

dimstyle_create

Create a dimension style with preset values and overrides, validating names, ranges, and block references before writing. Optionally set it as current for subsequent dimensions.

Instructions

Create a dimension style: preset values first, then overrides.

Refuses, before anything is written: an unknown preset; an override key outside the 33-variable whitelist (the 17 preset variables plus DIMTOL, DIMTP, DIMTM, DIMTOLJ, DIMTFAC, DIMLFAC, DIMRND, DIMATFIT, DIMTMOVE, DIMCLRD/E/T, DIMSAH, DIMBLK1/2, DIMCEN); a value outside its range (DIMDEC 0-8, sizes > 0, DIMTAD 0-4, DIMDSEP one character, lineweights an AutoCAD code); a name that already exists (use dimstyle_modify); a user DIMBLK/DIMBLK1/DIMBLK2 naming a block the drawing does not define (built-in arrowheads need none); a DIMTXSTY that is neither an existing text style nor a bundled preset (ISOCP, ISOCPEUR, ARIAL, ROMANS — those are created on both engines, textstyle_created; live, a preset whose font file the seat lacks is refused the same way, nothing written). On the live engine a write ActiveX still refuses after the style is added is rolled back — previous style current, the half-made entry deleted. With set_current the next dimension carries the style on both engines.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesNew dimension style name, e.g. ISO-25, ANSI, MECH-A3
presetNoiso-25 (ISO 129-1, 2.5 mm, comma) | ansi (ASME Y14.2, 3 mm, point); omit for the ISO-25 base
overridesNoDIM* variables applied on top of the preset, e.g. {DIMTXT: 3.5, DIMDSEP: '.', DIMTAD: 0}
set_currentNoAlso make it the current dimension style

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.6.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=false, so the description carries the burden and does so thoroughly: full list of pre-write refusals, atomicity ('before anything is written'), the live-engine rollback of a failed ActiveX write, and the fact that nothing is written on refusal. This is well beyond what the annotation provides.

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?

Front-loaded with the operation and the input ordering, then the refusal rules. Dense but largely earned; the long semicolon-chained sentence and comma splices reduce scannability slightly, though little is truly redundant.

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 values need not be explained, and for a mutation tool with only readOnlyHint=false the description supplies the missing failure modes, rollback behavior, and side effects. An agent has enough to call it correctly and predict refusals.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 100%, so the baseline is 3, but the description adds real semantics the schema lacks: the 33-variable override whitelist, per-variable ranges (DIMDEC 0-8, DIMDSEP one character, DIMTAD 0-4, lineweight codes), and the text-style acceptance rules. That meaningfully extends beyond the generic 'DIM* variables' schema text.

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 dimension style') and immediately scopes the two inputs (preset values first, then overrides). It also differentiates itself from the sibling dimstyle_modify by naming the condition under which that tool is the right choice.

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?

Explicitly routes the agent: duplicate names must go to dimstyle_modify, and set_current is described as the way to make the next dimension carry the style. The preset/override ordering gives operational guidance rather than just context.

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