Skip to main content
Glama
IBM

Physics MCP Server

by IBM

convert_unit

Convert numeric values between 62 unit types across 16 categories, including velocity, distance, mass, temperature, and data size. Accepts natural language queries.

Instructions

Convert a value from one unit to another.

Supports 62 unit types across 16 categories:
- Velocity: m/s, km/h, mph, ft/s, knots
- Distance: m, km, mi, ft, yd, in
- Mass: kg, g, lb, oz
- Force: N, kN, lbf
- Energy: J, kJ, cal, BTU, kWh
- Power: W, kW, hp
- Temperature: K, C, F
- Angle: rad, deg
- Pressure: Pa, kPa, bar, psi, atm
- Area: m², km², ft², acre
- Volume: m³, L, gal, ft³
- Time: s, min, hr, day
- Acceleration: m/s², g, ft/s²
- Torque: N·m, lb·ft, lb·in
- Frequency: Hz, kHz, MHz, GHz
- Data Size: B, KB, MB, GB

Enables natural language queries like:
- "Convert 60 mph to m/s"
- "How fast is 100 km/h in mph?"
- "Convert 10 kg to pounds"

Args:
    value: The numeric value to convert
    from_unit: Source unit (e.g., 'mph', 'kg', 'J')
    to_unit: Target unit (e.g., 'm/s', 'lb', 'kWh')

Returns:
    Dictionary with:
    - original_value: Input value
    - original_unit: Input unit
    - converted_value: Result value
    - converted_unit: Result unit
    - formatted: Human-readable string

Examples:
    >>> convert_unit(100, 'm/s', 'mph')
    {
        "original_value": 100,
        "original_unit": "m/s",
        "converted_value": 223.694,
        "converted_unit": "mph",
        "formatted": "100 m/s = 223.694 mph"
    }

    >>> convert_unit(60, 'mph', 'km/h')
    {
        "original_value": 60,
        "original_unit": "mph",
        "converted_value": 96.56064,
        "converted_unit": "km/h",
        "formatted": "60 mph = 96.56 km/h"
    }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
valueYes
from_unitYes
to_unitYes
Behavior4/5

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

With no annotations, the description discloses supported units, parameter purpose, return format, and examples. It does not cover error handling or idempotency, but overall is informative.

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?

The description is well-structured with bullet points, args/returns, and examples. It is slightly lengthy but every sentence adds value.

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?

Given no output schema, the description includes return fields, examples, and supported units, making it complete for a unit conversion tool.

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?

Input schema has 0% description coverage; the description lists parameter names, types, and example values, adding meaning that the schema lacks.

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 'Convert a value from one unit to another', lists supported units/categories, and distinguishes itself from sibling physics calculation tools.

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

Usage Guidelines3/5

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

The description implies usage for any unit conversion but does not explicitly specify when to use this tool over alternatives like list_unit_conversions, nor does it provide exclusion criteria.

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/IBM/chuk-mcp-physics'

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