Skip to main content
Glama
FullyDefined – AI for SOLIDWORKS

FullyDefined – AI for SOLIDWORKS

measure_part

Reads a SOLIDWORKS part's bounding box, overall size, volume, surface area, mass, density, centre of mass and solid body count in your chosen unit.

Instructions

Measure the part: bounding box (min and max corners along the model axes), overall size, volume, surface area, mass, density, centre of mass and number of solid bodies. Read-only.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "measure_part"
  }
}

Input Schema

NameRequiredDescriptionDefault
unitNoUnit for lengths (mm, cm, m, inch or ft)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It usefully states 'Read-only' and lists the measured outputs, but it omits prerequisites such as an open/active part, permission requirements, precision or formatting behavior, and failure modes.

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?

The description is a single front-loaded sentence listing the measurements, followed by a concise read-only qualifier. There is no redundant or filler wording.

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?

For a low-complexity, read-only measurement tool with one optional, fully documented parameter, the description is nearly complete. It leaves the active-document/part requirement and the exact return structure implicit, but the key measurement outputs are enumerated.

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%, and the unit parameter already documents acceptable values (mm, cm, m, inch, ft). The description adds no additional parameter meaning, such as the default unit or whether the unit affects derived values like mass and density, so the baseline 3 is appropriate.

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?

The description uses the specific verb 'Measure' with the resource 'part' and enumerates the exact properties returned, including bounding box, volume, mass, and centre of mass. It does not explicitly distinguish this from sibling tools such as measure_distance or check_interference, so it falls short of a 5.

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 description implies usage for obtaining part measurements but gives no explicit when-to-use guidance, prerequisites, or alternatives. 'Read-only' is useful context but does not route the agent between this and sibling measurement tools.

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