Skip to main content
Glama

Pressure unit converter

bpj_units_pressure
Read-onlyIdempotent

Convert pressure readings sharing one reference zero. Enter one of Pa, kPa, MPa, bar, mbar, atm, psi, Torr 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_pressure"
  }
}

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 readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds genuinely useful behavioral context beyond that: it discloses the return shape ("the equivalent value in every listed unit"), which matters because there is no output schema. It stops short of covering error behavior for an unsupported unit string.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the purpose and followed by the input contract; nothing is padded. The unit list is long but earns its place as the de facto enum.

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 stateless, read-only arithmetic conversion with rich annotations and no output schema, the definition covers what the tool does, what to supply, and what comes back. Remaining gaps are minor: case sensitivity of unit tokens, handling of unknown units, and output precision.

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%, so the description carries the burden. It does define the accepted vocabulary for the unit parameter (Pa through Torr), which the schema only repeats in a title and does not enforce as an enum. The value parameter gets no attention at all — the ±1e12 bounds and numeric type are left entirely to the schema, and precision or rounding behavior is unstated.

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 and resource ("Convert pressure readings") and enumerates every supported unit, so the agent knows instantly this is the pressure member of the unit-conversion family rather than temperature, torque, or force. The phrase "sharing one reference zero" further pins the domain to absolute-zero-aligned quantities.

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 "Convert pressure readings" and the instruction to enter one unit plus a value, so an agent can tell what it is for. However, there is no explicit when-to-use vs. when-not framing and no pointer to a sibling such as bpj_units_temperature_gap for cases involving deltas or affine scales, which is exactly the ambiguity the phrase "one reference zero" hints at but never resolves.

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.