Number Base Converter Skill

Overview

The input `value` is checked against the digits allowed for `from` before any conversion: base 8 accepts 0 to 7, base 16 accepts 0 to 9 and A to F, and so on up to base 36 with all letters. Letters are case-insensitive and a leading minus sign is allowed. A digit outside the base returns a 400, unlike JavaScript's `parseInt`, which stops at the first bad character. Both bases must be between 2 and 36; `from` defaults to 10.

Conversion is done by long division over the digit array instead of through a floating-point number, so results stay exact at any length. `decimal_value_exact` is the base-10 value as a string and is always exact. `decimal_value` is the same value as a JSON number for convenience; past 2^53 (9,007,199,254,740,992) it is rounded, so read `decimal_value_exact` for large inputs.

When `to` is set, `output_value` holds the converted digits in upper case, with `output_base` and `output_base_name`. Names are `binary`, `octal`, `decimal` and `hexadecimal` for 2, 8, 10 and 16, and `base-N` for every other base. When `to` is omitted, the response has no `output_value`; instead a `conversions` object gives `binary`, `octal`, `decimal`, `hexadecimal`, `base32` and `base36` together. Note that `base32` here is plain radix-32 digits (0-9, A-V), not RFC 4648 Base32 encoding.

Live Test Number Base Converter Skill Skill →

The tool

Once your client is connected to the VerveKit server, this appears in its tool list as NumberBaseConverterSkill. 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.

Tool call

{
  "name": "NumberBaseConverterSkill",
  "arguments": {
    "value": "255"
  }
}

You do not name the tool yourself; the model picks it. Asking about 255 in the terms this skill covers is enough for it to reach for NumberBaseConverterSkill 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"
    }
  }
}

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.

Argument	Type	Description
`value`Required	string	The number to convert
`from`Optional	integer	Source base (default: 10) default 10 · range 2–36
`to`Optional	integer	Target base (returns all common bases if not specified) range 2–36

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.

Result

{
  "status": "ok",
  "error": null,
  "data": {
    "input_value": "FF",
    "input_base": 16,
    "input_base_name": "hexadecimal",
    "decimal_value": 255,
    "decimal_value_exact": "255",
    "output_value": "255",
    "output_base": 10,
    "output_base_name": "decimal"
  }
}

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
`input_value`	string	`FF`	Original input value
`input_base`	number	`16`	Source base used for conversion
`input_base_name`	string	`hexadecimal`	Name of the input base, such as binary or hexadecimal
`decimal_value`	number	`255`	Value in decimal (base 10)
`decimal_value_exact`	string	`255`	The decimal value as an exact string. decimal_value is a number and cannot hold more than 15-16 significant digits; this field is exact for any input.
`output_value`	string	`255`	Converted value in target base
`output_base`	number	`10`	Base the value was converted to
`output_base_name`	string	`decimal`	Name of the output base

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 skill is not part of VerveKit. Check the catalog.
`429`	Out of credits, or a brief rate limit. The message tells them apart.

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

Use cases

Programming: Convert between binary, octal, decimal, and hexadecimal for programming and debugging
Computer Science Education: Teach number systems and base conversion concepts in educational tools
Data Encoding: Convert between different number representations for data encoding and decoding
Network Analysis: Work with hexadecimal values in network protocols and packet analysis

Other ways to use Number Base Converter Skill

Set up Number Base 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.

Call it as a REST APIOne HTTPS endpoint and an x-api-key header, with SDKs for Node, Python and .NET.APIVerve →Reference →

Google Sheets or ExcelA =VERVE() formula fills a column — no script, no export, recalculates in place.VerveSheets →Reference →

Ground an agent on itA cited, machine-checkable fact your model can't produce on its own.VerveContext →Reference →