API Hub MCP — 337+ Tools

convert_units

Convert between temperature, length, and weight units. Specify value, source unit, target unit, and unit type for quick conversions.

Instructions

Convert between measurement units: temperature, length, or weight.

Use this for quick unit conversions without lookup tables.
Supports Celsius/Fahrenheit/Kelvin, meters/feet/inches/km/miles,
and kg/lb/oz/stone.

Parameters:
    value     — Numeric value to convert.
    from_unit — Source unit (e.g. 'c', 'm', 'kg').
    to_unit   — Target unit (e.g. 'f', 'ft', 'lb').
    unit_type — 'temperature' (default), 'length', or 'weight'.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "value": "<value>",
      "from_unit": "<from_unit>",
      "to_unit": "<to_unit>"
    },
    "name": "convert_units"
  }
}

Input Schema

Name	Required	Default
`value`	Yes
`from_unit`	Yes
`to_unit`	Yes
`unit_type`	No	temperature

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.4.1Jun 22, 2026

TDQS

A4.3/5.0

Behavior3/5

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

No annotations are provided, so the description bears full burden. It lists supported units and parameters but does not disclose error handling, precision, or behavior for invalid inputs.

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?

The description is concise with a clear overview followed by a parameter list. Every sentence adds value, no fluff, and the purpose is stated upfront.

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?

The description covers supported conversions and parameter details. An output schema exists but its content is unknown; however, the description adequately equips an agent to select and use the tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has 0% description coverage, but the description explains each parameter's role and gives examples (e.g., 'c', 'm', 'kg'), adding significant meaning beyond the 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 'Convert between measurement units: temperature, length, or weight' with specific examples, distinguishing it from sibling conversion tools like area_convert or volume_convert.

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 advises 'Use this for quick unit conversions without lookup tables,' providing clear context for when to use this tool. However, it does not explicitly exclude usage or list alternatives among siblings.

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

Deploy Server