Skip to main content
Glama

Data rate unit converter

bpj_units_data_rate
Read-onlyIdempotent

Convert network bit rates and byte throughput. Enter one of bit/s, kbit/s, Mbit/s, Gbit/s, MB/s, MiB/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_data_rate"
  }
}

Input Schema

NameRequiredDescriptionDefault
unitYes
valueYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so safety behavior needs no restating. The description does add one genuinely useful behavioral fact — that the result is the equivalent in every listed unit, not a single target unit — which matters because no output schema exists. It says nothing about rounding or precision, however.

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, no waste, with the purpose front-loaded and the allowed units and return shape immediately following. Every clause carries information an agent needs.

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, non-destructive converter with no output schema, the description covers what the tool does, the accepted units, and the shape of the return. The remaining gap is edge-case behavior — unit string case sensitivity (the schema has no enum) and rounding of returned equivalents — which is minor but real.

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%, so the description carries the burden, and it does list the six accepted unit strings (bit/s, kbit/s, Mbit/s, Gbit/s, MB/s, MiB/s), which is the single most important parameter fact given there is no enum on the schema. It does not address case sensitivity or spelling tolerance, and says nothing about the value parameter's bounds or negative handling.

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 network bit rates and byte throughput") and scopes the domain to network/throughput rates, which distinguishes it from the broader information-unit sibling. It does not name an alternative tool outright, so it falls short of full sibling differentiation.

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 task (enter a value plus one unit, get all equivalents), but there is no explicit when-to-use vs. when-not guidance, no pointer to a related tool, and no exclusion such as "for data storage size use the information converter instead."

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.