Skip to main content
Glama

Digital storage unit converter

bpj_units_information
Read-onlyIdempotent

Convert decimal and binary storage sizes. Enter one of B, bit, kB, MB, GB, TB, KiB, MiB, GiB, TiB 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_information"
  }
}

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 readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered and the bar is low. The description adds genuinely new behavior: input is a single value/unit pair and the output is the equivalent expressed in every listed unit, which matters because there is no output schema.

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 tight sentences with the capability stated first and the input/output contract second; every clause carries information and nothing is padded or buried.

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, side-effect-free conversion tool with annotations covering safety and the description covering the return shape, the definition is nearly sufficient. The only gap is conversion precision or rounding behavior, which an agent might want to know but which is unlikely to cause a wrong invocation.

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 reported as 0%, but the two properties carry titles, and the unit title already lists the same allowed values the description repeats, so the description adds little beyond restating the accepted unit set. It clarifies that exactly one unit token must be supplied, but says nothing about numeric semantics such as fractional values or precision of the converted results.

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?

The description gives a specific verb (Convert) and resource (decimal and binary storage sizes) and enumerates the exact unit families it handles, so an agent can immediately tell this apart from the other unit-conversion siblings such as bpj_units_data_rate or bpj_units_capacity.

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 the phrase 'decimal and binary storage sizes'; there is no explicit statement of when to pick this tool over a related one (e.g. data rate vs. size) and no stated preconditions or exclusions. An agent can infer the domain from the unit list, but the definition does not route it.

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.