Skip to main content
Glama

Force unit converter

bpj_units_force
Read-onlyIdempotent

Convert force gauge readings in engineering units. Enter one of N, kN, mN, lbf, kgf, dyn 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_force"
  }
}

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?

The annotations already declare readOnly, idempotent, closed-world, and non-destructive, so the safety profile is covered. The description adds genuinely useful behavior beyond that: the result is returned in EVERY listed unit, which tells the agent what the (missing) output looks like. It omits the ±1e12 value bounds and any rounding/precision behavior.

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, front-loaded with the purpose, then the input rule and expected output. No filler and nothing repeated from the schema.

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 two-parameter converter with rich annotations and no output schema, the definition supplies enough: the domain, the valid unit vocabulary, and the shape of the return. Only the numeric limits and precision/rounding conventions are left unstated.

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 coverage is 0% and there is no enum on 'unit', so the description carries the full burden – and it does, enumerating all six accepted unit strings (N, kN, mN, lbf, kgf, dyn), which the schema alone does not constrain. The 'value' parameter only receives the implicit 'input value' meaning, with no mention of the allowed range, so it is not complete.

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?

States a specific verb and resource (convert force readings) plus the exact input unit set, which cleanly separates it from the neighboring torque, pressure, and energy converters. It stops short of naming a sibling to route away from, so a 4 rather than a 5.

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 only implied by 'Convert force gauge readings' – there is no explicit when-to-use statement, no exclusion pointing at bpj_units_torque for moment values, and no note that only one value/unit pair is accepted per call. The listed units hint at valid inputs but do not guide tool selection.

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.