Unit Converter Skill

Overview

A unit conversion API that replaces hand-maintained conversion tables in your code. It covers 185 units across 23 measures, so the everyday conversions are one call each: liters to gallons, miles per hour to kilometers per hour, Celsius to Fahrenheit, megabytes to gigabytes, psi to bar, pounds to kilograms, and kilowatt-hours to joules. Beyond length, area, mass, volume and temperature it handles time, speed, pace, pressure, digital storage, parts per million, frequency, angles, illuminance, volume flow rate and electrical units from volts and amperes to watts and kilowatt-hours. Results are rounded to 2 decimal places. On paid plans, precision returns up to 10 decimal places, so very small results no longer round to zero, and conversions=true returns the same value in every unit of its measure in one call, such as a mass in micrograms through metric tons.

Live Test Unit Converter Skill Skill →

The tool

Once your client is connected to the VerveKit server, this appears in its tool list as UnitConverterSkill. It is read-only and open-world — it fetches and never mutates anything on your side — so most clients call it without asking you to confirm.

{
  "name": "UnitConverterSkill",
  "arguments": {
    "value": "100",
    "from": "lb",
    "to": "kg"
  }
}

You do not name the tool yourself; the model picks it. Asking about 100 in the terms this skill covers is enough for it to reach for UnitConverterSkill on its own — naming it explicitly also works, and is the way to force the call.

Connecting

One server URL covers every skill in the catalog, including this one. Authorization is OAuth: the client opens a browser once, and there is no key to paste into a config file.

{
  "mcpServers": {
    "vervekit": {
      "url": "https://api.vervekit.com/v1/mcp"
    }
  }
}

https://api.vervekit.com/v1/mcp

Per-client setup — Claude, Cursor, VS Code, ChatGPT — is on the MCP setup page.

Arguments

These are the properties on the tool's inputSchema, so a well-behaved client validates them before the call is made. Premium arguments are accepted on every plan but only take effect on plans that include them.

What the model gets back

The result carries a structuredContent object matching the tool's declared outputSchema, so a client reads fields without parsing prose. status is "ok" and error is null on success; a null field means the value was not available for that input, not that the call failed.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37

{
  "status": "ok",
  "error": null,
  "data": {
    "result": {
      "result": 45.36,
      "from": "100 lb",
      "to": "kg"
    },
    "unitDefinitions": {
      "from": {
        "abbr": "lb",
        "measure": "mass",
        "system": "imperial",
        "singular": "Pound",
        "plural": "Pounds"
      },
      "to": {
        "abbr": "kg",
        "measure": "mass",
        "system": "metric",
        "singular": "Kilogram",
        "plural": "Kilograms"
      }
    },
    "conversions": {
      "mcg": 45359200000,
      "mg": 45359200,
      "g": 45359.2,
      "kg": 45.36,
      "mt": 0.05,
      "oz": 1600,
      "lb": 100,
      "t": 0.05
    }
  }
}

Response fields

Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.

Failure modes

Errors come back as tool errors carrying a sentence the model can act on, not a bare status code. Error handling covers the full list.

A call costs 1 credit each time the tool actually runs; a model that reasons about the tool without calling it costs nothing.

Supported Units

All 185 units across 23 measures. Units convert only within the same measure (length to length, pressure to pressure). Codes are case-sensitive: Mb is megabits and MB is megabytes. Miles per hour is m/h. Temperature codes also accept lowercase (c, f, k, r).

Use cases

Measurement Converters

Convert measurements such as weight, length, area, temperature, and more by using the Unit Converter API. Use the API to convert units between different systems

Unit Standardization

Standardize units across different systems by using the Unit Converter API. Convert units to a common standard for consistency and compatibility

Unit Calculation

Perform unit calculations by using the Unit Converter API to convert units in mathematical operations. Use the API to simplify unit conversions in calculations

Other ways to use Unit Converter Skill

Set up Unit Converter Skill on VerveKit, or reach the same source a different way. Your VerveKit account and credits work on all of them — one key, one balance.

Related

More in Data Conversion: