Skip to main content
Glama
Sign In
CAD MCP Server

CAD MCP Server

by 652036
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

add_dimension_linear

Define precise linear distances in CAD drawings by adding a dimension constraint between two points with a value and optional label.

Instructions

Add a dimension_linear 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": {
      "point_a": "<point_a>",
      "point_b": "<point_b>",
      "value": "<value>"
    },
    "name": "add_dimension_linear"
  }
}

Input Schema

NameRequiredDescriptionDefault
labelNo
valueYes
point_aYes
point_bYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

D1.3/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 of behavioral disclosure, and it discloses nothing. It does not say whether the constraint is persistent, what happens on failure, whether referenced points must exist, or what is returned.

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

Conciseness2/5

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

It is a single short sentence, but it is under-specified rather than concise — there is no wasted text because there is essentially no content. Brevity here reflects a lack of information, not efficient communication.

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?

For a 4-parameter mutation tool with 0% schema coverage, no annotations, and no output schema, the description is completely inadequate. It offers nothing an agent needs in order to invoke the tool correctly.

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

Parameters1/5

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

Schema coverage is 0% across 4 parameters, and the description adds no meaning for point_a, point_b, value, or label. An agent cannot tell from either source what these parameters should reference or how value is interpreted.

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 only restates the tool name ('Add' + 'dimension_linear constraint') without explaining what a linear dimension constraint does or what geometry it applies to. It is especially unhelpful given siblings like add_linear_dimension, add_aligned_dimension, and the other add_dimension_* tools, none of which are distinguished from this one.

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

Usage Guidelines1/5

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

There is no guidance on when to use this tool versus the many sibling dimension tools, no prerequisites, and no mention of required selections or sketch context. Nothing tells an agent how to choose between it and add_linear_dimension.

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