Skip to main content
Glama
FullyDefined – AI for SOLIDWORKS

FullyDefined – AI for SOLIDWORKS

set_dimension_style

Change the appearance of a drawing dimension by name: switch a round dimension between radius and diameter, or set its text colour as RGB values (0-255).

Instructions

Change how a drawing dimension looks: kind shows a round dimension as a radius or a diameter; text_color sets its text colour as {r, g, b} (0-255). The dimension is found by name among the views of the active sheet (list_drawing_views).

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": {
      "dimension": "<dimension>"
    },
    "name": "set_dimension_style"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoFor a round dimension
dimensionYesDimension name, e.g. RD1
text_colorNoColour of the dimension, 0-255 each

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden. It discloses the lookup mechanism (dimension found by name among the views of the active sheet), which is genuinely useful behavioral context, but says nothing about failure modes for an unknown name, whether the change is reversible, or permission/state 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?

Two dense sentences with the effect front-loaded and the lookup detail trailing. The parenthetical tool reference is slightly clunky but earns its place by explaining how the dimension name is resolved.

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

Completeness3/5

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

For a mutation tool with no annotations and no output schema, the description covers the two editable attributes and how the target is located. It is still thin on what the agent should expect on success/failure and on the interaction between 'kind' and non-round dimensions.

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 the baseline is 3. The description adds slight meaning by explaining that 'kind' applies to a round dimension and toggles radius versus diameter, but the text_color explanation ({r,g,b}, 0-255) largely restates the schema.

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

Purpose4/5

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

States a specific verb and resource ('Change how a drawing dimension looks') and immediately enumerates the two visual attributes it affects (kind, text_color). This separates it in spirit from value/precision tools like set_dimension_precision, though no sibling is named explicitly.

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

Usage Guidelines3/5

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

The parenthetical '(list_drawing_views)' tells the agent where dimension names come from, which is implied usage guidance. However, there is no explicit when-to-use versus set_dimension or set_dimension_precision, and no statement of prerequisites such as an active drawing document.

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