Skip to main content
Glama

Length unit converter

bpj_units_length
Read-onlyIdempotent

Convert design, drawing, and travel lengths. Enter one of m, mm, cm, km, in, ft, yd, mi, nmi 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_length"
  }
}

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 readOnly, idempotent, closed-world, and non-destructive, so the safety profile is covered. The description adds a genuine behavioral fact beyond that: the call returns the equivalent value in every listed unit (a single-call multi-unit expansion), not just one converted target. It omits precision/rounding behavior and error handling for invalid unit strings.

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 sentences, no filler, with the conversion purpose front-loaded and the input contract immediately after. Every clause carries information the agent needs to call the tool.

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?

With no output schema, the description correctly discloses the shape of the return (all listed units) and the input contract, which is enough for a simple, two-parameter pure-function converter. Minor omissions are rounding/precision and out-of-range handling for values below 0 or above 1e12.

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 the schema has no enum, so the description is the only place the accepted unit set is stated — it fully enumerates m, mm, cm, km, in, ft, yd, mi, nmi, and says exactly one must be supplied. It does not mention the value domain (0 to 1e12) enforced by the schema, which is a remaining gap.

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?

States a specific verb ('Convert') and resource ('lengths') and enumerates the exact unit set (m, mm, cm, km, in, ft, yd, mi, nmi), which cleanly separates it from dimension siblings like bpj_units_area, bpj_units_mass, or bpj_units_duration. An agent can identify it as the length converter without opening the schema.

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?

The description gives usable context ('design, drawing, and travel lengths') and tells the agent how to invoke it, but never states when not to use it or points to a sibling such as bpj_units_area for non-length measures. Usage is implied by the unit list rather than by explicit routing guidance.

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.