Skip to main content
Glama
Sign In
robosimtools-mcp

robosimtools-mcp

by RahulRajelli
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Mesh Mass Properties

robosim_mesh_mass_properties
Read-onlyIdempotent

Compute mass, center of mass, and inertia tensor from a closed STL or OBJ mesh using geometry integration. Input mesh file and density to obtain inertial properties.

Instructions

Compute mass, center of mass, and inertia tensor of a closed STL/OBJ mesh, integrated from the geometry. Coordinates in meters, density in kg/m^3.

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": {
      "filename": "<filename>",
      "content_base64": "<content_base64>"
    },
    "name": "robosim_mesh_mass_properties"
  }
}

Input Schema

NameRequiredDescriptionDefault
densityNo
filenameYes
content_base64YesMesh bytes, base64 (binary STL, ASCII STL, or OBJ).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already provide readOnlyHint, idempotentHint, and destructiveHint. The description adds useful behavioral details: units (meters, kg/m^3), integration method, and mesh closure requirement, going beyond what annotations provide.

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?

Two sentences with no wasted words. First sentence states purpose, second adds critical units. Front-loaded and efficient.

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

Completeness3/5

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

Explains what is computed and units, but does not specify return format (e.g., JSON object). For a computation tool with no output schema, this is a notable omission. Annotations cover safety but not output structure.

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 33% with only content_base64 described. The description adds meaning for density unit but does not clarify filename pattern or required parameters beyond schema. Provides some value but incomplete.

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 clearly states the verb 'Compute' and the resource 'mass, center of mass, and inertia tensor of a closed STL/OBJ mesh'. It distinguishes from sibling tools that deal with rotations, URDF conversions, etc.

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 closed STL/OBJ meshes but does not explicitly state when to use vs alternatives or when not to use. No exclusions or context for selection.

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