Skip to main content
Glama
Jambozx

OnlineCyberTools MCP (280+ filterable tools)

by Jambozx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

file_file_size_calculator

Read-onlyIdempotent

Convert data sizes between decimal and binary units, compare multiple file sizes, estimate transfer times, and calculate storage capacity fit. Handles common units like KB, MiB, and Mbps.

Instructions

File Size Calculator (Units, Compare, Transfer Time, Storage Fit). Convert a data size between SI/decimal units (KB, MB, GB, TB, PB, EB = powers of 1000) and IEC/binary units (KiB, MiB, GiB, TiB, PiB, EiB = powers of 1024), plus bit units, via four operations selected by "operation": convert (one size to every unit), compare (rank 2-32 sizes by bytes), transferTime (download/upload seconds at a given speed), and storageFit (how many items fit in a capacity). Use this for byte-unit math and bandwidth estimates; use conversion_base_converter for numeric radix conversion instead. Runs locally on the values you provide: read-only, non-destructive, contacts no external service, and is rate-limited (30 requests/minute for anonymous callers). Returns precise byte/bit counts plus human-readable decimal and binary strings; the result object's shape depends on the operation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
operationYesWhich calculation to run. Each operation reads a different subset of the other fields.
valueNoconvert only: the numeric size to convert. Pair with "unit".
unitNoconvert only: unit of "value". Decimal (KB=1000), binary (KiB=1024), or bit units.
itemsNocompare only: 2-32 sizes to rank by byte count.
sizeNotransferTime only: the amount of data to transfer.
speedNotransferTime only: the transfer rate; must be greater than zero.
targetCapacityNostorageFit only: total capacity to fill.
itemSizeNostorageFit only: size of one item; must be greater than zero.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
successNoAlways true on a 200; errors return 400/500 with an "error" string.
operationNoEcho of the requested operation.
resultNoOperation-specific payload.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed14 schema fields changedv0.5.1
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / itemSize
      Added value: +{
+  "additionalProperties": false,
+  "description": "storageFit only: size of one item; must be greater than zero.",
+  "properties": {
+    "unit": {
+      "description": "Size unit (MB, MiB, etc.).",
+      "type": "string"
+    },
+    "value": {
+      "description": "Numeric size.",
+      "minimum": 0,
+      "type": "number"
+    }
+  },
+  "required": [
+    "value",
+    "unit"
+  ],
+  "type": "object"
+}
    • addedInput schema / properties / items
      Added value: +{
+  "description": "compare only: 2-32 sizes to rank by byte count.",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "label": {
+        "description": "Optional name; defaults to \"Item N\".",
+        "type": "string"
+      },
+      "unit": {
+        "description": "Size unit (B, KB, MiB, Gbit, etc.).",
+        "type": "string"
+      },
+      "value": {
+        "description": "Numeric size.",
+        "minimum": 0,
+        "type": "number"
+      }
+    },
+    "required": [
+      "value",
+      "unit"
+    ],
+    "type": "object"
+  },
+  "maxItems": 32,
+  "minItems": 2,
+  "type": "array"
+}
    • addedInput schema / properties / operation / description
      Added value: +"Which calculation to run. Each operation reads a different subset of the other fields."
    • addedInput schema / properties / operation / enum
      Added value: +[
+  "convert",
+  "compare",
+  "transferTime",
+  "storageFit"
+]
    • addedInput schema / properties / size
      Added value: +{
+  "additionalProperties": false,
+  "description": "transferTime only: the amount of data to transfer.",
+  "properties": {
+    "unit": {
+      "description": "Size unit (B, KB, MiB, etc.).",
+      "type": "string"
+    },
+    "value": {
+      "description": "Numeric size.",
+      "minimum": 0,
+      "type": "number"
+    }
+  },
+  "required": [
+    "value",
+    "unit"
+  ],
+  "type": "object"
+}
    • addedInput schema / properties / speed
      Added value: +{
+  "additionalProperties": false,
+  "description": "transferTime only: the transfer rate; must be greater than zero.",
+  "properties": {
+    "unit": {
+      "description": "Speed unit: lowercase b = bits/s (Mbps), uppercase B = bytes/s (MBps).",
+      "enum": [
+        "bps",
+        "Kbps",
+        "Mbps",
+        "Gbps",
+        "Tbps",
+        "Kibps",
+        "Mibps",
+        "Gibps",
+        "Bps",
+        "KBps",
+        "MBps",
+        "GBps",
+        "TBps",
+        "KiBps",
+        "MiBps",
+        "GiBps"
+      ],
+      "type": "string"
+    },
+    "value": {
+      "description": "Numeric speed.",
+      "minimum": 0,
+      "type": "number"
+    }
+  },
+  "required": [
+    "value",
+    "unit"
+  ],
+  "type": "object"
+}
    • addedInput schema / properties / targetCapacity
      Added value: +{
+  "additionalProperties": false,
+  "description": "storageFit only: total capacity to fill.",
+  "properties": {
+    "unit": {
+      "description": "Size unit (GB, GiB, TB, etc.).",
+      "type": "string"
+    },
+    "value": {
+      "description": "Numeric size.",
+      "minimum": 0,
+      "type": "number"
+    }
+  },
+  "required": [
+    "value",
+    "unit"
+  ],
+  "type": "object"
+}
    • addedInput schema / properties / unit / description
      Added value: +"convert only: unit of \"value\". Decimal (KB=1000), binary (KiB=1024), or bit units."
    • addedInput schema / properties / unit / enum
      Added value: +[
+  "B",
+  "KB",
+  "MB",
+  "GB",
+  "TB",
+  "PB",
+  "EB",
+  "KiB",
+  "MiB",
+  "GiB",
+  "TiB",
+  "PiB",
+  "EiB",
+  "bit",
+  "Kbit",
+  "Mbit",
+  "Gbit",
+  "Tbit",
+  "Kibit",
+  "Mibit",
+  "Gibit",
+  "Tibit"
+]
    • addedInput schema / properties / value / description
      Added value: +"convert only: the numeric size to convert. Pair with \"unit\"."
    • addedInput schema / properties / value / minimum
      Added value: +0
    • changedInput schema / required
      Previous value: -[
-  "operation",
-  "value",
-  "unit"
-]New value: +[
+  "operation"
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "operation": {
+      "description": "Echo of the requested operation.",
+      "type": "string"
+    },
+    "result": {
+      "description": "Operation-specific payload.",
+      "properties": {
+        "binary": {
+          "description": "convert: size in B/KiB/MiB/GiB/TiB/PiB/EiB (numbers).",
+          "type": "object"
+        },
+        "bits": {
+          "description": "convert: total bits as a string.",
+          "type": "string"
+        },
+        "bytes": {
+          "description": "convert/compare: byte count as a string (BigInt-safe).",
+          "type": "string"
+        },
+        "bytesPrecise": {
+          "description": "convert: exact byte count as a string.",
+          "type": "string"
+        },
+        "decimal": {
+          "description": "convert: size in B/KB/MB/GB/TB/PB/EB (numbers).",
+          "type": "object"
+        },
+        "humanBinary": {
+          "description": "convert: best-fit binary string, e.g. 1.4 GiB.",
+          "type": "string"
+        },
+        "humanDecimal": {
+          "description": "convert/compare: best-fit decimal string, e.g. 1.5 GB.",
+          "type": "string"
+        },
+        "humanDuration": {
+          "description": "transferTime: human duration, e.g. 1m 04s.",
+          "type": "string"
+        },
+        "input": {
+          "description": "convert: the echoed value and unit.",
+          "type": "object"
+        },
+        "items": {
+          "description": "storageFit: whole items that fit as a string; compare instead returns an array of index/label/bytes/humanDecimal/percentOfMax.",
+          "type": "string"
+        },
+        "remainderBytes": {
+          "description": "storageFit: leftover bytes after the fit, as a string.",
+          "type": "string"
+        },
+        "seconds": {
+          "description": "transferTime: transfer time in seconds.",
+          "type": "number"
+        },
+        "size": {
+          "description": "transferTime: value, unit and bytes of the data.",
+          "type": "object"
+        },
+        "speed": {
+          "description": "transferTime: value, unit and bytesPerSecond of the rate.",
+          "type": "object"
+        }
+      },
+      "type": "object"
+    },
+    "success": {
+      "description": "Always true on a 200; errors return 400/500 with an \"error\" string.",
+      "type": "boolean"
+    }
+  },
+  "type": "object"
+}
  2. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description adds value beyond annotations by noting rate limiting (30 req/min for anonymous), local execution, and that the result shape depends on operation. No contradiction with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is approximately 100 words, well-structured with key information front-loaded. Every sentence contributes value, though it could be slightly more concise without losing clarity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (8 parameters, nested objects, 4 operations, output schema), the description is remarkably complete. It covers purpose, behavior, usage guidelines, and limitations, leaving no critical gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description adds meaning by explaining how operation determines which fields to use and briefly describing each operation's purpose, enhancing understanding beyond schema descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly specifies the tool's purpose: converting data sizes between SI, IEC, and bit units via four operations (convert, compare, transferTime, storageFit). It distinguishes from sibling conversion_base_converter, avoiding ambiguity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when to use this tool (byte-unit math and bandwidth estimates) and when to use an alternative (conversion_base_converter for numeric radix conversion). Also provides context for each operation.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools