Skip to main content
Glama
Sign In
CAD MCP Server

CAD MCP Server

by 652036
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

add_dimension_diameter

Adds a diameter dimension constraint to a circle in an AutoCAD drawing, given its circle ID and numeric value.

Instructions

Add a dimension_diameter constraint.

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": {
      "circle_id": "<circle_id>",
      "value": "<value>"
    },
    "name": "add_dimension_diameter"
  }
}

Input Schema

NameRequiredDescriptionDefault
valueYes
circle_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

D1.8/5.0
Behavior1/5

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

No annotations are provided, so the description carries the full burden, and it discloses nothing: not whether an entity must pre-exist, whether the target must be a circle, whether the constraint persists, or what happens on failure. Bare minimum not met.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single short sentence with no waste, but there is hardly any content to be concise about – the brevity reflects under-specification rather than discipline.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no annotations, no output schema, 0% parameter description coverage, and crowded sibling space (multiple add_*dimension and constraint tools), the description leaves an agent unable to determine correct targets, units, or workflow.

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

Parameters2/5

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

Schema coverage is 0%, so the description must compensate, but it says nothing about what circle_id or value mean (units? edge reference? identifier format?). Schema provides only property names and types.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Add a dimension_diameter constraint' restates the tool name with virtually no added specificity. Among dozens of sibling add_* tools, it does not distinguish what target this dimension applies to (the schema's circle_id hints it, but the description does not).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No indication of when to use this versus add_radius_dimension, add_diameter_dimension, add_aligned_dimension, or other dimension siblings. No prerequisites, no context for choosing this tool.

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