Skip to main content
Glama

Sheet metal mass

bpj_material_sheet_metal_mass
Read-onlyIdempotent

Find the mass of flat metal blanks from plan dimensions, thickness, quantity, 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": {
      "length": "<length>",
      "width": "<width>",
      "thickness": "<thickness>",
      "density": "<density>",
      "quantity": "<quantity>"
    },
    "name": "bpj_material_sheet_metal_mass"
  }
}

Input Schema

NameRequiredDescriptionDefault
widthYes
lengthYes
densityYes
quantityYes
thicknessYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds nothing behavioral beyond that: it does not state the output unit (presumably kg given density in kg/m3), rounding, or that the calculation assumes a solid rectangular blank with no cutouts. For a deterministic calculator this is a modest but real gap.

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?

A single front-loaded sentence with no filler or redundancy. It is efficient, though the brevity leaves room that could have been spent on units or output format without becoming bloated.

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?

This is a simple five-parameter pure calculation with no output schema, so the bar is not high. Still, the description never says what the result is (mass in kg? per blank or total?) or that quantity multiplies the per-blank mass, which is the one ambiguity an agent would want resolved before calling.

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 0%, so the description must carry parameter meaning. It does map its concepts onto all five parameters (plan dimensions to length/width, thickness, quantity, density), which is more than the schema text offers. However, it omits units and the quantity-multiplier semantics, which are only recoverable from the schema titles (mm, kg/m3), so it only partially compensates for the coverage gap.

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 description states a specific verb and resource: 'Find the mass of flat metal blanks.' It also names the driving inputs (plan dimensions, thickness, quantity, density), which separates it from generic mass tools like bpj_eng_center_of_mass. It stops short of explicitly contrasting itself with any sibling, so it lands at 4 rather than 5.

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?

There is no when-to-use or when-not-to-use guidance, no mention of when a sibling such as bpj_eng_center_of_mass or bpj_units_mass would be preferable, and no stated preconditions. The phrase 'flat metal blanks' implies a scope, but the agent must infer that this excludes non-flat or non-metal parts on its own.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.