codecalc

by The-40-Thieves

Overview Schema Source Related Servers Discussions Admin

Python

Local

List Units

list_units

Read-onlyIdempotent

Enumerate all supported unit aliases and spellings for converting between measurement units.

Instructions

List every supported unit alias — all aliases and spellings — for convert_units.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.11.0Sep 9, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "title": "list_unitsDictOutput",
+  "type": "object"
+}

Changed3 schema fields changedv0.2.0Aug 19, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```
addedInput schema / title
```
Added value: +"list_unitsArguments"
```

changedOutput schema / (root)

Previous value: -{
-  "additionalProperties": true,
-  "type": "object"
-}New value: +null

First observedv0.1.0Aug 7, 2026

TDQS

A4.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false, covering safety. The description adds the detail that output includes aliases and spellings, which is useful but not extensive. For a trivial read-only listing tool, this is acceptable but not rich.

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?

A single sentence with zero waste, front-loading the core action and resource. It is appropriately sized for a tool with no parameters.

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

Completeness5/5

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

For a zero-parameter read-only listing tool with an output schema, the description fully covers what an agent needs to know: it lists all unit aliases for convert_units. No missing information is required to call it correctly.

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?

The tool has zero parameters, so the baseline is 4. The description does not need to explain parameters, and it correctly omits any mention since there are none.

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 the action (list), the resource (every supported unit alias), and the scope (all aliases and spellings for convert_units). This distinguishes it from sibling tools like list_languages and list_execution_providers without ambiguity.

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?

The description implies usage: it is the go-to tool for discovering unit aliases before using convert_units. While it does not explicitly state when not to use it or name alternatives, the context makes its purpose clear, and no sibling tool overlaps in function.

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