Skip to main content
Glama
SolidWorks MCP Python

SolidWorks MCP Python

by locense

Measure Entities

measure_entities
Read-onlyIdempotent

Measure faces, edges, or vertices in the active SolidWorks model to check feature size or position, including area, perimeter, length, radius, and distance or angle between two entities.

Instructions

Measure faces, edges or vertices of the active model with SolidWorks' Measure tool.

One face gives area and perimeter; one edge its length, and radius and diameter for an arc; two entities give the distance and angle between them. Use it to check a feature's size or position; for the whole model, use verify_model. Needs: an open part or assembly. Read-only. It clears the selection afterwards. Returns: data with selected and the values in metres, square metres and radians (distance_m, angle_rad, length_m, radius_m, diameter_m, area_m2, perimeter_m; for two entities is_parallel).

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": {
      "input_data": "<input_data>"
    },
    "name": "measure_entities"
  }
}

Input Schema

NameRequiredDescriptionDefault
input_dataYesWhat to measure. `entities` (one or two) is required, each "face:x,y,z", "edge:x,y,z", "vertex:x,y,z" (a point on it, in metres) or a name like "Edge<1>".

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered; the description nonetheless adds a genuinely non-obvious side effect ("It clears the selection afterwards") plus the prerequisite of an open document. It does not describe failure behavior (e.g., what happens if an entity reference cannot be resolved), which keeps it below a 5.

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 purpose, then labeled "Needs:" and "Returns:" blocks, which scans well. The explicit enumeration of every return key is partly redundant with the output schema, so there is some trimming left on the table.

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

Completeness5/5

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

For a one-parameter read-only measurement tool with a rich nested schema and an output schema, the definition covers purpose, prerequisites, side effects, alternative tool and units. Nothing an agent needs in order to call it correctly is missing.

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 entity string formats, unit convention and one-vs-two entity semantics are already documented in the schema. The description's entity-outcome sentence (face gives area/perimeter, two entities give distance and angle) largely restates that, adding little meaning beyond the structured field.

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?

The description opens with a specific verb and resource ("Measure faces, edges or vertices of the active model") and immediately differentiates its scope from the sibling `verify_model`. An agent can distinguish this from model-wide verification tools without opening any schema.

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

Usage Guidelines5/5

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

It states the concrete use case ("check a feature's size or position") and names the alternative for the excluded case ("for the whole model, use `verify_model`"). It also states a prerequisite ("Needs: an open part or assembly"), so both when-to-use and when-not-to-use are covered.

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