Skip to main content
Glama

Acceleration unit converter

bpj_units_acceleration
Read-onlyIdempotent

Convert motion sensor acceleration. Enter one of m/s2, cm/s2, ft/s2, g0, Gal 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_acceleration"
  }
}

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 readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds useful behavior beyond that: it constrains the accepted input units and states that the result is the equivalent value in every listed unit, i.e. a full conversion table rather than a single target unit. It doesn't mention rounding or output format, but that is minor for a pure conversion.

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, nothing wasted, and the input constraint plus return behavior are both front-loaded.

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?

With only two parameters, no output schema, and rich annotations, the description supplies the critical missing piece (valid unit tokens) and explains the return semantics ('equivalent value in every listed unit'). Details like numeric precision or the shape of the returned multi-unit result are left implicit.

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 the unit parameter has no enum, so the description carries the burden; it compensates by enumerating exactly the five accepted unit tokens, which is the single most important thing an agent needs to call this correctly. The 'value' parameter is only covered by the schema's numeric bounds, which the schema already supplies.

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 uses a specific verb ('Convert') and a specific resource domain ('motion sensor acceleration'), and enumerates the five supported units. It implicitly separates itself from siblings like bpj_units_speed or bpj_units_force by naming the acceleration domain, though it never explicitly says so.

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?

It tells the agent what to supply ('Enter one of m/s2, cm/s2, ft/s2, g0, Gal') and what comes back, which implies the usage pattern. There is no explicit when-to-use, when-not-to-use, or routing guidance toward any alternative tool.

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.