Skip to main content
Glama
FullyDefined – AI for SOLIDWORKS

FullyDefined – AI for SOLIDWORKS

set_dimension_precision

Set how many decimals drawing dimensions display, for one dimension by name or every dimension in a view, optionally including tolerance decimals. Only the display changes, not the model's values.

Instructions

Set how many decimals drawing dimensions show: one dimension by its name (list_drawing_views(view=...)), or every dimension in a view. tolerance_decimals sets the decimals of their tolerances too (default: left as they are). Only the display changes, not the model's values; dimensions added later keep the template's decimals, so call it last. Each dimension's precision is read back.

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": {
      "decimals": "<decimals>"
    },
    "name": "set_dimension_precision"
  }
}

Input Schema

NameRequiredDescriptionDefault
viewNoEvery dimension in this view (or give dimension)
decimalsYesDecimals shown, 0 to 8
dimensionNoA dimension name, e.g. RD1 (or give view)
tolerance_decimalsNoDecimals of the tolerance, 0 to 8 (default: unchanged)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and mostly succeeds: it discloses that only display changes and model values are untouched (non-destructive), that the tolerance default is 'left as they are', that later-added dimensions are not affected, and that precision is read back. Missing only error behavior for an unknown dimension name or permission requirements.

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 purpose, then scope, then side effects, then ordering advice — a sensible priority order. The parenthetical asides and the final sentence about reading back are slightly compressed but each sentence adds information; nothing is 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?

No output schema exists, and the description compensates by stating that each dimension's precision is read back. For a 4-parameter display-only mutation, the important unknowns (does it touch the model, does it affect future dimensions, what is the return) are all addressed; only failure modes are unstated.

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 100%, so the baseline is 3, but the description adds real meaning: it explains the view-vs-dimension alternative (one or the other, not both) and restates the tolerance_decimals default as 'left as they are' rather than merely 'unchanged'. It does not add units or format details beyond the schema's 0–8 range.

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 ('Set how many decimals drawing dimensions show') and immediately scopes it to two mutually exclusive targets: a single dimension by name or every dimension in a view. This distinguishes it from the adjacent 'set_dimension_style' and 'set_dimension' siblings, which operate on other properties of the same objects.

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?

Gives a concrete ordering rule: 'dimensions added later keep the template's decimals, so call it last.' It also points at 'list_drawing_views(view=...)' as the way to discover the view argument. It does not explicitly contrast with 'set_dimension_style', but the when-to-call guidance is unusually concrete for this catalog.

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