Skip to main content
Glama
Sign In
sketchflow-mcp

sketchflow-mcp

by 4Ship-ca
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

model_mass

Calculate per-part and assembly mass properties—material, density, volume, mass, centre of gravity, inertia, parts list, and tip direction—to assess 3D model mass and stability.

Instructions

Mass properties of the 3D model: per part material, density, volume, mass, centre of gravity and inertia; assembly total mass, centre of gravity, inertia and whether it stands on its base (or which way it tips); the parts list (quantities, part numbers, materials, masses); and the material library. Set materials with model_build {op:"set", id, material:"steel"} or meta:{material, density, fill, part_no, supplier, notes, quantity}, or a model default with {op:"material", material}.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "model_mass"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0-beta.1

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden, and it does disclose the exact result content including per-part metrics, assembly stability/tip direction, parts-list fields, and the material library. It also signals that material changes happen through model_build rather than this tool, though it never explicitly declares read-only behavior or result formatting.

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 sentences: the first front-loads purpose and packs the return inventory into a semicolon list; the second gives a useful pointer for changing materials. The material-setting sentence is slightly tangential to invoking model_mass, but it is not wasted and the description remains compact.

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?

For a zero-parameter, no-output-schema tool, the description gives a comprehensive inventory of what comes back—per-part and assembly mass properties, parts list, and material library—so an agent knows what to expect. It stops short of describing result structure or format, but that is a minor gap given the tool's simplicity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Zero parameters; the empty schema has 100% coverage by definition, and no parameter meaning needs to be explained. The baseline of 4 applies, and the description adds no misleading parameter claims.

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

Purpose4/5

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

The first sentence names the resource (mass properties of the 3D model) and enumerates the exact metrics returned—per-part material, density, volume, mass, centre of gravity, inertia; assembly totals and stability; parts list; material library. That is specific enough to separate it from geometry-description or query siblings, though it never explicitly contrasts itself with them.

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?

No sentence states when to call model_mass versus alternatives such as model_describe or model_query; the closest guidance is the implied use of retrieving mass properties. The material-setting instructions point to model_build but describe changing data rather than when to invoke this tool.

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