GadgetHumans API Hub

unit_convert

Convert a value between units of length, mass, volume, area, speed, temperature, data and time. Pure CPU, instant.

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>"
    },
    "name": "unit_convert"
  }
}

Input Schema

Name	Required	Description
`to`	No	Target unit
`from`	No	Source unit
`value`	Yes	Value to convert

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 8, 2026
RemovedNov 6, 2026

Changed4 schema fields changedNov 3, 2026

addedInput schema / properties / from

Added value: +{
+  "description": "Source unit",
+  "type": "string"
+}

addedInput schema / properties / to

Added value: +{
+  "description": "Target unit",
+  "type": "string"
+}

addedInput schema / properties / value

Added value: +{
+  "description": "Value to convert",
+  "type": "number"
+}

addedInput schema / required
```
Added value: +[
+  "value"
+]
```

AddedNov 2, 2026

TDQS

B3.3/5.0

Behavior3/5

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

With no annotations, the description carries the full behavioral burden. "Pure CPU, instant" usefully indicates local computational behavior and expected performance, but there is no information about precision, invalid or incompatible units, error handling, or the form of the result.

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 compact and front-loaded with the operation and supported domains. The second short sentence adds behavioral information without unnecessary elaboration.

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

Completeness3/5

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

This is minimally adequate for a simple three-parameter converter because the operation and supported domains are clear. However, the crowded sibling set, lack of accepted-unit syntax, unspecified output behavior, and unexplained optional from/to parameters leave gaps in reliable selection and invocation.

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

Parameters3/5

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

Schema coverage is 100%, so the baseline is 3, and the description's measurement categories add only broad context for the unit parameters. It does not document accepted unit names or symbols, provide an example, or clarify why from and to are optional despite being logically necessary for conversion.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb and resource: converting values between units, with an explicit list of supported measurement categories. It does not distinguish this general converter from overlapping siblings such as convert_units, area_convert, or speed_convert.

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

Usage Guidelines2/5

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

The category list implies the tool's general scope, but there is no actual selection guidance. In particular, it does not explain when to prefer this tool over convert_units or the specialized conversion siblings, nor when conversion is unsupported.

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

All GadgetHumans API Hub tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.