Overview
File Size Formatter works by dividing byte values by the appropriate divisor (1024 for binary, 1000 for decimal) to calculate sizes in various units. Automatically selects the most appropriate unit or allows manual specification.
Live Test File Size Formatter Skill Skill →
The tool
Once your client is connected to the VerveKit server, this appears in its tool list as FileSizeFormatterSkill. 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": "FileSizeFormatterSkill",
"arguments": {
"bytes": "1073741824"
}
}You do not name the tool yourself; the model picks it. Asking about 1073741824 in the terms this skill covers is enough for it to reach for FileSizeFormatterSkill 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/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 |
|---|---|---|
bytesRequired | integer | Number of bytes to format range 0–∞ |
unitOptional | string | Specific target unit (optional, auto-selects best unit if not specified)autoBKBMBGBTBPBEB+2 |
precisionOptional | integer | Decimal places (0-10) default 2 · range 0–10 |
standardOptional | string | Standard to use: binary (1024) or decimal (1000)binarydecimaldefault binary |
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": {
"bytes": 1073741824,
"formatted": "1 GiB",
"value": 1,
"unit": "GiB",
"standard": "binary",
"precision": 2,
"conversions": {
"B": 1073741824,
"KiB": 1048576,
"MiB": 1024,
"GiB": 1,
"TiB": 0,
"PiB": 0,
"EiB": 0,
"ZiB": 0,
"YiB": 0
}
}
}
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 |
|---|---|---|---|
bytes | number | 1073741824 | Original byte value in numeric format |
formatted | string | 1 GiB | Formatted file size with unit as human-readable string |
value | number | 1 | Numeric value in the selected or auto-determined unit |
unit | string | GiB | File size unit used in the conversion (e.g., GiB, MB) |
standard | string | binary | Standard used for conversion: binary or decimal |
precision | number | 2 | Decimal places applied to the formatted value |
conversionsPremium | object | {…} | Complete conversion table with values across all units |
conversions.BPremium | number | 1073741824 | The size expressed in bytes |
conversions.KiBPremium | number | 1048576 | The size expressed in kibibytes (1024 bytes) |
conversions.MiBPremium | number | 1024 | The size expressed in mebibytes |
conversions.GiBPremium | number | 1 | The size expressed in gibibytes |
conversions.TiBPremium | number | 0 | The size expressed in tebibytes |
conversions.PiBPremium | number | 0 | The size expressed in pebibytes |
conversions.EiBPremium | number | 0 | The size expressed in exbibytes |
conversions.ZiBPremium | number | 0 | The size expressed in zebibytes |
conversions.YiBPremium | number | 0 | The size expressed in yobibytes |
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 2 credits each time the tool actually runs; a model that reasons about the tool without calling it costs nothing.
Use cases
- File Management
- Display file sizes in user-friendly formats in file managers and storage applications
- Storage Analytics
- Format storage usage data in dashboards and analytics reports
- Data Transfer
- Show download and upload sizes in appropriate units during file transfers
- API Responses
- Convert byte sizes to readable formats in API responses and data exports
Other ways to use File Size Formatter Skill
Set up File Size Formatter 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: