Skip to main content
Glama

WritersLogic business agents

minor-units

ISO 4217 minor units: decimal amount to integer minor units and back — Converts up to 200 money amounts between decimal strings and integer minor units (cents, yen, fils) using the ISO 4217 exponent from the SIX Group list, for an agent about to send an amount to a payment API. Returns the exponent, the integer minor amount and the canonical decimal string; JPY is 0, KWD and BHD are 3, CLF is 4. An amount with more fraction digits than the currency allows fails with

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": {
      "items": "<items>"
    },
    "name": "minor-units"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and largely meets it: it discloses the 200-item cap, the authoritative exponent source (SIX Group), the shape of the result (exponent, integer minor amount, canonical decimal string), and failure behavior on over-precise amounts. The failure clause is cut off mid-sentence ('fails with '), so the exact error contract is unknown, and it does not state what happens for a currency missing from the list absent an override.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One dense paragraph, front-loaded with the core conversion claim before the batch limit, return shape, exponent examples and error note. No filler sentences. The trailing sentence is truncated, which leaves the paragraph ending abruptly rather than closing cleanly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, and the description does describe the return fields, which is the most important gap filled. However, the error condition is left unfinished, and precedence between amount, minor and exponent override is left to the schema rather than stated. For a batch conversion tool feeding a payment API, the incomplete error contract is a meaningful omission.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The reported 0% coverage reflects only the top-level 'items' wrapper; the nested properties in the schema are in fact documented, and the description still adds meaning beyond them by pinning real exponent values (JPY 0, KWD and BHD 3, CLF 4) that an agent would otherwise have to look up. It also clarifies the practical consequence of the rounding enum when fraction digits exceed the exponent. This is domain knowledge, not a restatement of the schema.

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 opening states a precise verb and resource: converting decimal amounts to integer minor units and back, batched up to 200, grounded in the ISO 4217 exponent list. The name 'minor-units' alone is opaque, so the description is doing real work. It stops short of differentiating itself from plausible siblings such as cash-rounding or other currency utilities.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It names the operating context explicitly — 'for an agent about to send an amount to a payment API' — which tells the agent when this is the right call. It also explains when the rounding parameter matters (excess fraction digits). There are no stated exclusions or pointers to alternative tools for adjacent needs like display rounding or currency conversion.

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.

Resources