Skip to main content
Glama

Mass unit converter

bpj_units_mass
Read-onlyIdempotent

Convert parcel, recipe, and material masses. Enter one of kg, g, mg, t, lb, oz to return the equivalent value in every listed unit.

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": {
      "value": "<value>",
      "unit": "<unit>"
    },
    "name": "bpj_units_mass"
  }
}

Input Schema

NameRequiredDescriptionDefault
unitYes
valueYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already establish readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is fully covered. The description adds one genuinely useful behavioral fact beyond that – the call returns the equivalent in *every* listed unit, not just a single target – but says nothing about rounding precision, output shape details, or how invalid unit strings are handled.

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 short sentences, front-loaded with the purpose and followed by the accepted-unit vocabulary and return behavior. Nothing is repeated from the schema and no sentence is wasted.

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 two-parameter, annotation-covered, stateless converter with no output schema, the definition covers purpose, valid unit tokens, and return semantics adequately. The only residual gaps are precision/rounding and unit-string casing, which are minor for this tool class.

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?

Schema coverage is 0% and the unit parameter has no enum, so the description carries the burden of enumerating the accepted tokens (kg, g, mg, t, lb, oz) – exactly the information the schema omits and the most likely source of call errors. It does not mention case sensitivity or hint at the value bounds (0 to 1e12) present in the schema, so it stops short of full compensation.

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?

"Convert parcel, recipe, and material masses" gives a specific verb plus resource and immediately bounds the scope to the six mass units, so the agent knows exactly what domain this covers. It does not explicitly distinguish itself from the closely named sibling bpj_units_mass_flow, leaving that disambiguation to the tool name rather than the description.

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 implied rather than stated: the agent can infer this is the tool for converting a mass value between kg/g/mg/t/lb/oz. There is no explicit when-to-use, when-not-to-use, or pointer to the many sibling unit converters (area, length, mass_flow) that would confirm the selection rule.

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.