Skip to main content
Glama

Density unit converter

bpj_units_density
Read-onlyIdempotent

Convert mass densities of liquids and solids. Enter one of kg/m3, g/cm3, g/L, lb/ft3, lb/USgal 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_density"
  }
}

Input Schema

NameRequiredDescriptionDefault
unitYes
valueYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world behavior, so the description only needs to add value beyond that. It does so by disclosing the output behavior: a single input yields the equivalent value in every listed unit, which clarifies that no output-unit parameter exists. It stops short of mentioning rounding or precision, which is the only remaining gap.

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 with zero filler. The purpose is front-loaded and the parameter/output mechanics follow immediately, so nothing needs to be re-read or parsed out of order.

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?

This is a simple deterministic converter with full annotation coverage and only two required scalar parameters, so the definition is nearly complete: what it does, what to supply, and what comes back are all stated. The absence of any precision or rounding statement is the one meaningful omission for a numeric conversion tool.

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?

With schema description coverage at 0%, the description has to carry the load, and it does enumerate the five accepted unit strings for the `unit` parameter. It says less about `value` aside from the implied density magnitude; the non-negative bounds visible in the schema are not restated, so this is strong but not exhaustive.

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 opens with a specific verb and resource, 'Convert mass densities of liquids and solids', and enumerates the exact unit families accepted. Combined with the unit list, an agent can easily tell this density converter apart from siblings like bpj_units_mass or bpj_units_flux_density even though those names are never mentioned.

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 by the mechanics of the tool: supply one of the listed units and a value to get a full conversion table. There is no explicit statement of when to prefer this over related tools, no prerequisites, and no error-condition guidance beyond the unit enumeration.

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.