Skip to main content
Glama

pressure_convert

Read-onlyIdempotent

Convert pressure values between common units including Pa, hPa, kPa, bar, atm, psi, torr, mmHg, and inHg for accurate comparisons and calculations.

Instructions

Convert pressure between Pa, hPa, kPa, bar, atm, psi, torr, mmHg, inHg.

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>"
    },
    "name": "pressure_convert"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoTarget unit (omit for all).
fromNoSource unit (default pa).
valueYesPressure value to convert.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds no behavioral details such as return format or behavior when 'to' is omitted, but for a pure deterministic conversion tool with full annotation coverage, this is minimally adequate.

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?

A single efficient sentence with the core action and supported units front-loaded. Every element earns its place, with zero waste.

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 simple three-parameter unit converter with full schema descriptions and rich annotations, the description is nearly complete. The only minor gaps are return format and the exact effect of omitting 'to', though the schema covers the latter.

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 100%, establishing a baseline of 3, but the description adds meaningful value by enumerating the supported pressure units that are not represented as enums in the schema. It does not explain the omit/default behavior for 'from' and 'to', but the schema already does that.

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 states a specific verb ('Convert') and resource ('pressure') and enumerates the supported units, which clearly distinguishes it from sibling converters such as convert_length, convert_temperature, and convert_speed.

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 pressure-specific unit list, but the description gives no explicit guidance on when to use this tool versus alternatives, nor any conditions or exclusions. The schema provides defaults, but the description itself does not route the agent.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools