Skip to main content
Glama
onshape-jamcp

onshape-jamcp

Measure part or Part Studio

get_part_properties
Read-only

Measure a part’s bounding box, volume, surface area, mass, and centroid in the configured length unit to verify dimensions and orientation after modeling.

Instructions

Measure geometry: the axis-aligned bounding box (min/max/size) plus volume, surface area, mass and centroid per part, in the configured length unit. Use it to verify dimensions and orientation after modeling. Mass is only meaningful if the part has a material assigned in Onshape.

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": {
      "document_id": "<document_id>",
      "element_id": "<element_id>"
    },
    "name": "get_part_properties"
  }
}

Input Schema

NameRequiredDescriptionDefault
tightNoUse Onshape's TIGHT bounding box (default). The quick REST box can be too large on swept surfaces such as threads (0.5 mm per side on an M10 nut); false returns that quick box.
part_idNoMeasure only this part (from list_parts).
element_idYesElement (tab) ID: the string after /e/ in the Onshape URL. Get it from get_document.
document_idYesOnshape document ID: the 24-character hex string after /documents/ in the document URL. Get it from list_documents.
workspace_idNoWorkspace ID (the string after /w/ in the URL). Optional - defaults to the document's main workspace.
configurationNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the read-only, open-world safety profile, so the description is free to spend words elsewhere and does: it discloses that mass is only meaningful when a material is assigned, a non-obvious failure mode. The tight-box behavior is useful but is largely restated from the schema's own parameter description, so it is not fully additive.

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?

Three sentences, front-loaded with the measurement scope, then the use case, then the caveat — no filler. Slightly heavy on output enumeration when an output schema exists, but each clause carries information.

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?

With an output schema present, the description need not explain return values and correctly focuses on scope, units and the material precondition. For a 6-parameter read tool it is close to complete; only alternative-tool routing and configuration-evaluation behavior remain unaddressed.

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 83%, so the schema already documents tight, part_id, element_id, document_id, workspace_id and configuration. The description adds only the unit convention ("in the configured length unit") and the per-part scoping implication; it adds no detail on tight or configuration semantics beyond what the schema states. Baseline 3 applies.

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?

"Measure geometry: the axis-aligned bounding box (min/max/size) plus volume, surface area, mass and centroid per part" states a specific verb and enumerates the exact resource/outputs. An agent knows precisely what this returns, and the scope (per part, part studio) separates it from document-level or feature-level siblings.

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?

"Use it to verify dimensions and orientation after modeling" gives a clear application context, and the mass caveat sets a precondition. However, there is no when-not guidance and no routing to a plausible alternative such as get_body_details, which an agent could reasonably confuse this with.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.