Skip to main content
Glama

Speed unit converter

bpj_units_speed
Read-onlyIdempotent

Convert ground and nautical speeds. Enter one of m/s, km/h, mph, kn, ft/s 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_speed"
  }
}

Input Schema

NameRequiredDescriptionDefault
unitYes
valueYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/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 genuinely useful output disclosure that no structured field provides: the result is returned 'in every listed unit', which tells the agent to expect a multi-unit result rather than a single value.

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, both load-bearing, with the conversion behavior front-loaded and the unit list directly attached to the input requirement. Nothing is 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, annotation-covered converter with no output schema, this is nearly complete: input units, value semantics, and output shape are all covered. Minor gaps remain around invalid-unit handling and accepted unit string format (case, abbreviations).

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 0% and the unit parameter has no enum, so the description carries real weight by enumerating the five accepted unit strings. It does not cover the numeric range constraints (0 to 1e12) or case sensitivity, but it compensates well for the missing enum.

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 (convert) and a specific resource (ground and nautical speeds), and its unit list (m/s, km/h, mph, kn, ft/s) makes it unmistakably the speed converter rather than the acceleration or frequency siblings in the same family.

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 ground and nautical speeds' and by the enumerated units, but there is no explicit when-to-use/when-not statement and no acknowledgment of related converters (e.g. acceleration) that could be confused with speed.

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.