Burs-IA Utils

Convertir tamaño de datos

convert-data-size

Read-onlyIdempotent

Convierte tamaño de datos entre unidades (bit, B, kB, MB, GB, TB, PB, KiB, MiB, GiB, TiB, PiB, kbit, Mbit, Gbit). Sin "to" devuelve todas. Cuándo: hay que convertir una cantidad entre unidades con factores de definición exactos. No para: convertir tasa de datos entre unidades (convert-data-rate). Efectos secundarios: ninguno (solo lectura, sin red, sin estado guardado). Determinista: la misma entrada da la misma salida. Límites: entrada JSON de hasta 64 KB, 1 s por llamada, resultado de hasta 1 MB.

EN: Converts data size between units (bit, B, kB, MB, GB, TB, PB, KiB, MiB, GiB, TiB, PiB, kbit, Mbit, Gbit). Without "to", every unit is returned. Exact definitional factors; results to 12 significant digits. When: a quantity has to be converted between units with exact definitional factors. Not for: converting data rate between units (convert-data-rate). Side effects: none (read-only, no network access, no stored state). [EN completo / full EN: inputSchema.description]

Input Schema

Name	Required	Description
`to`	No	Target unit (omit for all) (string; optional; up to 20 chars).
`from`	Yes	Source unit: bit, B, kB, MB, GB, TB, PB, KiB, MiB, GiB, TiB, PiB, kbit, Mbit, Gbit (string; required; up to 20 chars).
`value`	Yes	Value to convert (number; required).

Output Schema

Name	Required	Description
`to`	No
`from`	No
`value`	No	any JSON value
`result`	No	any JSON value

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 2, 2026
- addedInput schema / properties / from / examples
```
Added value: +[
+  "GiB"
+]
```
- addedInput schema / properties / value / examples
```
Added value: +[
+  1
+]
```

Changed1 schema field changedNov 1, 2026

addedInput schema / description

Added value: +"EN: Converts data size between units (bit, B, kB, MB, GB, TB, PB, KiB, MiB, GiB, TiB, PiB, kbit, Mbit, Gbit). Without \"to\", every unit is returned. Exact definitional factors; results to 12 significant digits. When: a quantity has to be converted between units with exact definitional factors. Not for: converting data rate between units (convert-data-rate). Side effects: none (read-only, no network access, no stored state). Deterministic: the same input gives the same output. Limits: JSON input up to 64 KB, 1 s per call, result up to 1 MB."

First observedNov 1, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the 'side effects: none' sentence restates structured data. What it genuinely adds is determinism, 12-significant-digit precision, and hard limits (64 KB input, 1 s per call, 1 MB result), which are real behavioral context beyond the annotations.

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

Conciseness3/5

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

The when/not-for/limits structure is well front-loaded, but the entire content is duplicated verbatim in Spanish and English, roughly doubling length without adding information. A pointer to the EN copy in inputSchema.description would suffice.

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

Completeness4/5

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

With an output schema available and full parameter coverage, the description only needs routing and behavioral context — both present, including precision and resource limits. Complete enough that an agent can call it correctly on the first try.

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

Parameters3/5

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

Schema description coverage is 100% and each parameter is individually documented, so the baseline applies. The description's only added semantic is that omitting 'to' returns all units — useful but already implied by the schema's 'omit for all'.

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?

Names a specific verb (converts) and resource (data size), enumerates the supported units, and explicitly excludes the sibling convert-data-rate. An agent can distinguish it from the other ~20 convert-* tools without opening any schema.

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?

Explicit 'Cuándo' clause states the condition (exact definitional factors) and 'No para' names the alternative tool and the excluded case (data rates). This is the when/when-not/alternative pattern at its clearest.

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

All Burs-IA Utils tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?