Skip to main content
Glama

Torque unit converter

bpj_units_torque
Read-onlyIdempotent

Convert rotating equipment torque. Enter one of N.m, N.cm, lbf.ft, lbf.in, kgf.cm 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_torque"
  }
}

Input Schema

NameRequiredDescriptionDefault
unitYes
valueYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly and idempotent, so the safety profile is covered. The description adds the key behavioral fact that the tool is a one-shot converter returning the equivalent in every listed unit, which is real return-value context given no output schema exists.

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, zero filler, with the action and the accepted units front-loaded before the return behavior. Nothing is redundant or padded.

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 stateless converter with no output schema, the description supplies the input vocabulary and describes what comes back, which is close to complete. Only the absence of any note on precision or the numeric input limits keeps it from a 5.

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 must carry the parameter burden; it does document the accepted unit tokens for the `unit` parameter, but that list is already present in the schema title, and the `value` parameter's numeric bounds (plus/minus 1e12) are left entirely to the schema with no hint in the description.

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 rotating equipment torque") and enumerates the accepted units, making it immediately distinguishable from the many sibling unit converters such as bpj_units_force or bpj_units_power. An agent can select it 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?

"Enter one of N.m, N.cm, lbf.ft, lbf.in, kgf.cm" implies how to call it, but there is no explicit when-to-use or when-not-to-use guidance versus neighbors like force or power, and no mention that this is a pure computation with no data dependencies.

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.