Skip to main content
Glama

numfmt

Read-only

Convert numbers between plain, SI, and IEC binary unit systems. Parse human-readable size strings back to raw numbers for byte count humanization or input parsing.

Instructions

Convert numbers between plain, SI (K, M, G), and IEC binary (Ki, Mi, Gi) unit systems. Read-only, no side effects. Parses human-readable strings with SI/IEC suffixes back to raw numbers. Returns JSON with the converted value by default; use --raw for plain output. Use to humanize byte counts or parse user-supplied size strings. Not for formatted string output — use 'printf' for general formatting. See also 'printf'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
from_unitNoInput unit system.none
max_linesNoMaximum JSON records to emit.
numbersNoNumbers to convert. Defaults to whitespace tokens from stdin.
precisionNoDigits after the decimal point before trimming zeros.
rawNoWrite converted numbers without a JSON envelope.
to_unitNoOutput unit system.none
Behavior4/5

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

Annotations already provide readOnlyHint=true. Description adds 'no side effects' and explains output format (JSON by default, plain with --raw). No contradictions.

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?

Three concise sentences, front-loaded with main purpose. Every sentence provides value without redundancy.

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?

No output schema, but description explains output format. Differentiates from many sibling tools. Could mention that --raw also affects parsing behavior, but complete enough given the tool's simplicity.

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 coverage is 100%, so description adds minimal extra meaning beyond parameter names and defaults. The overall behavior is explained, but no parameter-specific details beyond schema.

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 clearly states it converts numbers between SI, IEC, and plain unit systems, and parses human-readable strings. It distinguishes itself from siblings like 'printf' by specifying it's not for general formatting.

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

Usage Guidelines5/5

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

Explicitly states when to use (humanize byte counts, parse size strings) and when not (use 'printf' for formatted output). Includes a 'See also' reference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/caseSHY/AI-CLI'

If you have feedback or need assistance with the MCP directory API, please join our Discord server