File Size Formatter SkillFile Size Formatter Skill

OnlineCredit Usage:1 per callTool:FileSizeFormatterSkill

The tool

File Size Formatter provides comprehensive file size conversions across all units from bytes to yottabytes, with support for both IEC binary and SI decimal standards.

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

Tool call
{
  "name": "FileSizeFormatterSkill",
  "arguments": {
    "bytes": "1073741824"
  }
}

What that looks like in a conversation

You don't name the tool — the model picks it. Asking about 1073741824 in the terms this source covers is enough for it to reach for FileSizeFormatterSkill on its own.

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.

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

Per-client setup — Claude Desktop, 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.

ArgumentTypeExampleDescription
bytesRequiredinteger1073741824Number of bytes to format
unitstringGBSpecific target unit (optional, auto-selects best unit if not specified) One of: auto, B, KB, MB, GB, TB, PB, EB.
precisioninteger2Decimal places (0-10)
standardstringbinaryStandard to use: binary (1024) or decimal (1000) One of: binary, decimal.

What the model gets back

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

Result
{
  "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
    }
  }
}

Fields

Fields marked Premium need a paid plan. On a plan without them the key is absent rather than wrong, so a model never reasons over a substituted value.
FieldTypeExampleDescription
bytesnumber1073741824Original byte value in numeric format
formattedstring1 GiBFormatted file size with unit as human-readable string
valuenumber1Numeric value in the selected or auto-determined unit
unitstringGiBFile size unit used in the conversion (e.g., GiB, MB)
standardstringbinaryStandard used for conversion: binary or decimal
precisionnumber2Decimal places applied to the formatted value
conversionsPremiumobject{…}Complete conversion table with values across all units
conversions.BPremiumnumber1073741824The size expressed in bytes
conversions.KiBPremiumnumber1048576The size expressed in kibibytes (1024 bytes)
conversions.MiBPremiumnumber1024The size expressed in mebibytes
conversions.GiBPremiumnumber1The size expressed in gibibytes
conversions.TiBPremiumnumber0The size expressed in tebibytes
conversions.PiBPremiumnumber0The size expressed in pebibytes
conversions.EiBPremiumnumber0The size expressed in exbibytes
conversions.ZiBPremiumnumber0The size expressed in zebibytes
conversions.YiBPremiumnumber0The size expressed in yobibytes

Failure modes

Errors come back as tool errors with a sentence the model can act on, not a bare status code.

StatusWhat it means
400 / 422The arguments didn't validate. The message names the offending one.
401The OAuth session is invalid or expired — reconnect the server.
403Out of credits. Not a bad key — the month's allowance is spent.
404This skill isn't part of VerveKit. Check the catalog.
429Brief rate limit. Retrying after a moment succeeds.

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.

Call it as a REST APIOne HTTPS endpoint and an X-API-Key header, with SDKs for Node, Python and .NET.APIVerveReference →
Use it in Google Sheets or ExcelA =VERVE() formula fills a column — no script, no export, recalculates in place.VerveSheetsReference →
Ground an agent on itA cited, machine-checkable fact your model can't produce on its own.VerveContextReference →

Frequently asked questions

Do I have to tell the agent to use FileSizeFormatterSkill?

No. The tool's name and description are in the model's context once the server is connected, so it selects the tool when the question calls for it. Naming it explicitly works too and is useful when you want to force the call.

Does connecting the server expose every tool at once?

Yes — one connection lists the whole VerveKit catalog. Clients with a tool budget can usually filter the list; the credit cost is per call, so an unused tool costs nothing.

What does a call cost?

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

Is there a REST version of this?

Yes — the same source is available as a plain HTTPS endpoint on APIVerve, linked above. Same data, same credits, same account.

What's Next?

Continue your journey with these recommended resources

Was this page helpful?