Skip to main content
Glama
Sign In
CAD MCP Server

CAD MCP Server

by 652036
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_mass_properties

Calculate mass properties from a solid's simplified volume and material density to estimate weight, center of mass, and related physical values.

Instructions

Return mass properties based on simplified volume and material density.

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": {
      "solid_id": "<solid_id>"
    },
    "name": "get_mass_properties"
  }
}

Input Schema

NameRequiredDescriptionDefault
solid_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior3/5

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

No annotations, so the description carries the burden. It discloses a meaningful behavioral model: output is based on a simplified volume and material density, implying approximation rather than exact measurement. It doesn't state read-only nature, units, or that the solid must exist/have material assigned.

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?

Single efficient sentence, front-loaded with the verb and result. No filler, though it is short enough that it could carry more without bloat.

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

Completeness2/5

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

A measurement/computation tool with no annotations, no output schema, and undocumented parameters. The description does not cover return structure, units, material prerequisite, or the simplified-volume caveat's implications, leaving real gaps.

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?

One parameter (solid_id) with 0% schema description coverage. The description implies the input is a solid but doesn't document solid_id's format or source. With only 1 param and no enum/nesting, baseline 3 with modest gap is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a clear verb (return) and resource (mass properties) tied to a solid via simplified volume and material density. However, it does not distinguish itself from close siblings like measure_volume, measure_centroid, or measure_moment_of_inertia, which an agent could confuse with this.

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

Usage Guidelines2/5

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

No when-to-use guidance. Given the dense cluster of measurement siblings (measure_volume, measure_moment_of_inertia, measure_centroid), the description should route the agent, but it offers no conditions or alternatives.

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