Skip to main content
Glama
FullyDefined – AI for SOLIDWORKS

FullyDefined – AI for SOLIDWORKS

set_units

Sets the default length unit (mm, inch, cm, or m) used when a SOLIDWORKS tool input omits a unit, keeping modeling dimensions consistent.

Instructions

Set the default length unit, mm, inch, cm or m, used when a tool's unit input is left out.

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": {
      "unit": "<unit>"
    },
    "name": "set_units"
  }
}

Input Schema

NameRequiredDescriptionDefault
unitYesNew default length unit

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses the downstream effect (applies as a fallback when a unit input is omitted), but says nothing about scope or persistence — whether the default is per-document, per-session, or global, and whether it retroactively affects existing geometry.

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

Conciseness5/5

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

One sentence, front-loaded with the verb and resource, zero filler. The qualifying clause is short and carries real information.

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 single-parameter setter with no output schema, the core is covered, but the persistence scope of a 'default' setting is exactly what an agent would need and it is absent.

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 coverage is 100% and the enum already constrains the values, so the description's enumeration adds little. It does clarify that the value becomes the default rather than applying to one operation, which is modest added meaning.

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?

Specific verb+resource: 'Set the default length unit', with the allowed values enumerated (mm, inch, cm, m). This is clearly distinct from nearby setters like set_dimension_precision or set_color, though it never names a sibling to contrast with.

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 clause 'used when a tool's unit input is left out' implies the reason to call it, but there is no explicit when-to-use trigger, no statement about when not to call it, and no alternative tool mentioned.

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