mcp-gnu-units
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| infoA | Discovery / health-check entrypoint: report availability and version info. Returns seven keys: |
| find_unitsA | Search the GNU units database for units whose name or definition contains a keyword. Basic substring search over the 3000+ unit GNU units database (TODO §14.1). A
hit is any unit whose name OR definition text contains Returns:
Enriching each hit lets you search AND triage in a single call instead of a follow-up lookup per unit. Example: find_units("horsepower") -> {"query":"horsepower","count":9,"results":[{"name":"horsepower", "definition":"550 foot pound force / sec","kind":"unit", "dimension":"kg m^2 / s^3","base_value":"745.7 kg m^2 / s^3"}, ...]} |
| convertA | Convert a value or unit expression from one unit to another (GNU units engine, TODO §16). The universal conversion core: one tool covers every category (length, mass,
time, temperature, area, volume, energy, power, speed, data, …) plus compound
expressions like Returns: |
| convert_to_siA | Reduce a value or unit expression to its SI base units (GNU units engine, TODO §17). Rewrites any expression in terms of the database's primitive/base units — kg, m,
s, A, K, mol, cd, and the like — collapsing all derived and prefixed units. This
is how you see what a quantity really is dimensionally: Returns: |
| define_unitA | Show a single unit/prefix/constant's definition, kind, dimension, and base value (TODO §13). Looks up one name in the GNU units database and reports exactly what it is and
what it reduces to — the inspect/"define" counterpart to Returns an object with:
Errors cleanly (isError) when the name is not defined in the database. Example: define_unit("newton") -> {"name":"newton","kind":"unit","definition":"kg m / s^2", "base_value":"1 kg m / s^2","dimension":"kg m / s^2"} |
| list_prefixesA | List every SI and binary prefix in the GNU units database with its multiplier (TODO §13). Enumerates all defined prefixes — the SI decimal ladder ( Returns: |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool has a clearly distinct purpose: info for metadata, convert for arbitrary unit conversion, convert_to_si for SI base reduction, define_unit for single-unit inspection, find_units for database search, and list_prefixes for prefix enumeration. The only potential overlap is convert vs convert_to_si, but their outputs and use cases are explicitly differentiated.
Three tools follow a clear verb_noun pattern (define_unit, find_units, list_prefixes) and two more are related verb phrases (convert, convert_to_si), but info is a noun outlier and convert is a bare verb. The set is still mostly consistent and readable.
Six tools is well within the ideal 3–15 range for a unit conversion and database inspection server. Each tool covers a distinct core capability and none feels redundant or missing.
The surface covers conversion, SI reduction, single-unit definition, keyword search, prefix listing, and service metadata. Minor gaps exist, such as no direct way to list all units or browse by dimension, but agents can approximate these via find_units with broad queries.