Unit Converter MCP
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| convert_temperatureB | Convert temperature between units. |
| convert_angleB | Convert angle between units. |
| convert_lengthB | Convert length between units. |
| convert_energyB | Convert energy between units. |
| convert_forceB | Convert force between units. |
| convert_pressureB | Convert pressure between units. |
| convert_powerB | Convert power between units. |
| convert_speedB | Convert speed between units. |
| convert_areaB | Convert area between units. |
| convert_massB | Convert weight between units. |
| convert_volumeB | Convert volume between units. |
| convert_computer_dataB | Convert computer storage between units. |
| convert_densityB | Convert density between units. |
| convert_timeB | Convert time between units. |
| convert_batchA | Perform multiple unit conversions in a single batch request. Each request in the batch should contain:
Returns a structured response with individual results for each conversion, including success/failure status and either converted values or error messages. |
| list_supported_unitsB | List all supported units for each conversion type or for a specific type. |
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 16 tools
Every tool has a clearly distinct purpose targeting specific physical quantities (e.g., length, mass, temperature) or operations (batch conversion, listing units). There is no ambiguity—an agent can easily select the correct tool based on the conversion type needed.
All tools follow a consistent verb_noun pattern with 'convert_' or 'list_' prefixes, using snake_case throughout. This predictable naming scheme makes it easy for agents to understand and navigate the toolset without confusion.
With 16 tools, the count is borderline high for a unit conversion server, as many tools could be consolidated into a single parameterized tool. While each tool serves a distinct conversion type, the proliferation of similar tools might feel heavy and could be streamlined for better usability.
The toolset provides comprehensive coverage for unit conversion, including all common physical quantities (length, mass, temperature, etc.), batch operations, and listing supported units. There are no obvious gaps—agents can perform any conversion task within the domain without dead ends.