Skip to main content
Glama

Typographic size unit converter

bpj_units_typographic_size
Read-onlyIdempotent

Convert CSS absolute lengths, PostScript points, and picas. Enter one of in, mm, pt, pc, cssPx 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_typographic_size"
  }
}

Input Schema

NameRequiredDescriptionDefault
unitYes
valueYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and closedWorld, so safety behavior is covered. The description adds a real behavioral fact beyond that: the result is returned 'in every listed unit', i.e. a single call returns the full multi-unit conversion rather than one target unit, which shapes how an agent should consume the output.

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 no padding: purpose first, invocation second. Every clause contributes actionable information and nothing is repeated from the schema or annotations.

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, side-effect-free converter this covers the essentials: what it converts, accepted input tokens, and that output spans all listed units. Without an output schema, the description could still mention precision or the exact result shape, but no critical calling information is missing.

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% and there is no enum on the `unit` property, so the description carries the burden — and it does enumerate the accepted unit tokens (in, mm, pt, pc, cssPx), which is genuinely additive. However, it says nothing about the `value` parameter, such as the 0-to-1e12 bounds or what happens with out-of-range or unsupported input.

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 opens with a specific verb and resource ('Convert CSS absolute lengths, PostScript points, and picas'), which tells an agent exactly what domain of unit conversion is handled. It is distinguishable from generic siblings like bpj_units_length by the typographic framing, though it never names a sibling to contrast against.

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 guidance is procedural ('Enter one of in, mm, pt, pc, cssPx'), which is helpful for invocation but says nothing about when to prefer this over the general length converter in the sibling catalog. No prerequisites, exclusions, or alternative routing are stated.

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.