Skip to main content
Glama

Mass Properties

mass_properties
Read-only

Computes volume, surface area, centroid, bounding box, and inertia tensor of a shaped object; returns mass when density is provided.

Instructions

Mass properties of a shaped object: volume (mm³), surface area (mm²), centroid, bounding box, inertia tensor. If density (kg/mm³) is given, also returns mass (kg). Steel = 7.9e-6, aluminum = 2.7e-6, ABS = 1.05e-6.

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": {
      "handle": "<handle>"
    },
    "name": "mass_properties"
  }
}

Input Schema

NameRequiredDescriptionDefault
handleYes
densityNo
workspaceNoRun this call in this named workspace

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.7
    • addedInput schema / properties / workspace
      Added value: +{
      +  "default": "",
      +  "description": "Run this call in this named workspace",
      +  "title": "Workspace",
      +  "type": "string"
      +}
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds real value beyond that: exact output units (mm³, mm²), the conditional nature of the mass result, and the density unit convention (kg/mm³) with reference values for common materials.

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 compact sentences, with the primary output list front-loaded and the conditional mass behavior second. The three reference densities are arguably optional but are short and reduce lookup errors.

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 no output schema, the description does the necessary work of enumerating return fields and their units. It is nearly complete for a read-only measurement tool; only the provenance/validity of `handle` and failure behavior are unstated.

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 only 33% (only `workspace` is documented). The description fully compensates for `density` by giving its unit and concrete example values, but the required `handle` parameter is never explained — the agent must infer it is an object reference from sibling tools.

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?

Names the exact computed quantities (volume, surface area, centroid, bounding box, inertia tensor) with units, plus the conditional mass output. An agent can distinguish this from siblings like bounding_box or measure_distance without opening the schema, since the full result set is enumerated.

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?

Usage is only implied by 'of a shaped object' plus the density conditional. There is no statement of when to prefer this over bounding_box (which overlaps on bounding box) or measure_distance/check_shape, and no prerequisites such as requiring a valid handle from a prior modeling call.

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