Skip to main content
Glama

Paper grammage unit converter

bpj_units_paper_grammage
Read-onlyIdempotent

Convert paper and fabric mass per area. Enter one of g/m2, kg/m2, oz/yd2, lb/1000ft2 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_paper_grammage"
  }
}

Input Schema

NameRequiredDescriptionDefault
unitYes
valueYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuine behavioral context beyond them: the call returns the equivalent value in every listed unit, which tells the agent the response is a multi-unit conversion rather than a single value. It omits rounding/precision behavior, keeping it below a 5.

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 operational instruction. Nothing is repeated and nothing extraneous is included.

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, single-purpose converter with no output schema, the description supplies the units, the input pattern, and the shape of the result. Only precision/rounding conventions and the exact unit-string sensitivity are missing, which are minor for this 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?

Schema description coverage is 0% and there is no enum, so the description carries the burden — and it does enumerate the accepted unit strings (g/m2, kg/m2, oz/yd2, lb/1000ft2), which the schema itself does not constrain. The numeric value parameter is left to obvious inference, and the 0-to-1e12 bound and exact-string requirement are not restated.

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 gives a specific verb and resource — converting mass-per-area values for paper and fabric — which is more precise than a generic 'unit converter'. The four named units make the scope concrete and distinguish it from siblings like bpj_units_area or bpj_units_density. It does not explicitly name a sibling to route away from, so a 4 rather than a 5.

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?

'Enter one of g/m2, kg/m2, oz/yd2, lb/1000ft2 to return the equivalent value' gives clear input instructions but no when-to-use vs. when-not-to-use guidance and no mention of alternative tools for adjacent quantities. Usage is only implied by the domain wording.

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.