Overview
Unit Converter works by using formulas to convert units from one to another. Using a well defined set of units, it returns the converted value to the desired unit.
Live Test Unit Conversion for AI Agents Source →
The tool
Once your client is connected to the VerveContext server, this appears in its tool list as UnitConversionforAIAgents. 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": "UnitConversionforAIAgents",
"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 source covers is enough for it to reach for UnitConversionforAIAgents on its own — naming it explicitly also works, and is the way to force the call.
Connecting
One server URL covers every source 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": {
"vervecontext": {
"url": "https://api.vervecontext.com/v1/mcp"
}
}
}https://api.vervecontext.com/v1/mcpPer-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.
| Argument | Type | Description |
|---|---|---|
valueRequired | number | The value to convert |
fromRequired | string | The unit to convert from |
toRequired | string | The unit to convert to |
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.
{
"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"
}
}
}
}
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.
| Field | Type | Example | Description |
|---|---|---|---|
result | object | {…} | The conversion result. The numeric value is nested at result.result; result.from and result.to echo the units |
result.result | number | 45.36 | Converted numeric value in target units |
result.from | string | 100 lb | Original value with source unit abbreviation |
result.to | string | kg | Target unit abbreviation for conversion |
unitDefinitions | object | {…} | The full definitions of the source and target units |
unitDefinitions.from | object | {…} | Definition of the source unit, including its singular and plural names |
unitDefinitions.from.abbrPremium | string | lb | Source unit abbreviation code |
unitDefinitions.from.measurePremium | string | mass | Physical quantity being measured from |
unitDefinitions.from.systemPremium | string | imperial | Measurement system of source unit |
unitDefinitions.from.singularPremium | string | Pound | Singular name of source unit |
unitDefinitions.from.pluralPremium | string | Pounds | Plural name of source unit |
unitDefinitions.to | object | {…} | Definition of the target unit, including its singular and plural names |
unitDefinitions.to.abbrPremium | string | kg | Target unit abbreviation code |
unitDefinitions.to.measurePremium | string | mass | Physical quantity being measured to |
unitDefinitions.to.systemPremium | string | metric | Measurement system of target unit |
unitDefinitions.to.singularPremium | string | Kilogram | Singular name of target unit |
unitDefinitions.to.pluralPremium | string | Kilograms | Plural name of target unit |
Why ground on it
A model can produce something that looks like this answer from its training data, and be confidently out of date or simply wrong. This source returns the current value in a shape you can check, which is the difference between an answer you can cite and one you have to hedge.
Point an evaluation at result.result: it is the field most worth pinning a claim to, and it is either present and current or absent — never plausibly invented.
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.
| Status | What it means |
|---|---|
400 / 422 | The arguments did not validate. The message names the offending one. |
401 | The OAuth session is invalid or expired — reconnect the server. |
403 | Blocked by a key restriction or an IP allow-list. Never a bad identity. |
404 | This source is not part of VerveContext. Check the catalog. |
429 | Out of credits, or a brief rate limit. The message tells them apart. |
A call costs 2 credits each time the tool actually runs; a model that reasons about the tool without calling it costs nothing.
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 Conversion for AI Agents
Set up Unit Conversion for AI Agents on VerveContext, or reach the same source a different way. Your VerveContext account and credits work on all of them — one key, one balance.
Related
More in Data Conversion: