Skip to main content
Glama
Sign In

Burs-IA Utils

by io.github.soyeladice-svg
OverviewDiscussionsAdmin

Descomprimir (gzip, deflate, brotli)

zlib-decompress
Read-onlyIdempotent

Descomprime datos base64 en gzip, zlib/deflate, deflate sin cabecera o Brotli (detecta gzip y zlib). La salida se limita a 1 MB, así que las «bombas» de compresión fallan de forma segura. Devuelve texto UTF-8 si es válido, si no base64. Cuándo: hay que convertir bytes o texto a esta codificación, o desde ella, con exactitud y sin adivinar. No para: comprimir texto o bytes con gzip (zlib-compress). 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: Decompresses base64 data in gzip, zlib/deflate, raw deflate or Brotli (auto-detects gzip and zlib headers). Output is capped at 1 MB, so compression bombs fail safely. Returns UTF-8 text when valid, else base64. When: bytes or text have to be converted to or from this encoding exactly, without guessing. [EN completo / full EN: inputSchema.description]

Input Schema

NameRequiredDescriptionDefault
dataYesCompressed data (base64) (string; required).
formatNoFormat (auto detects gzip/zlib headers) (optional; one of: auto, gzip, deflate, deflate-raw, brotli; default "auto").auto

Output Schema

NameRequiredDescriptionDefault
textNo
formatNo
output_bytesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / data / examples
      Added value: +[
+  "H4sIAAAAAAAAA8vIBACsKpPYAgAAAA=="
+]
  2. Changed1 schema field changed
    • addedInput schema / description
      Added value: +"EN: Decompresses base64 data in gzip, zlib/deflate, raw deflate or Brotli (auto-detects gzip and zlib headers). Output is capped at 1 MB, so compression bombs fail safely. Returns UTF-8 text when valid, else base64. When: bytes or text have to be converted to or from this encoding exactly, without guessing. Not for: compressing text or bytes with gzip (zlib-compress). 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."
  3. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive and closed-world, yet the description adds real value beyond them: 1 MB output cap, safe failure on compression bombs, UTF-8 vs base64 return selection, determinism, and hard limits (64 KB input, 1 s per call). That is exactly the operational context an agent needs before calling.

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?

Content is front-loaded and organized into labeled sections, but the full Spanish text plus a duplicated English rendering doubles the length, and the trailing '[EN completo / full EN: inputSchema.description]' is a dangling pointer rather than useful text. Several claims (read-only, deterministic, limits) are restated across sections.

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?

An output schema exists, so return-value detail is not required, and the description still covers formats, auto-detection, return encoding, size caps and rate limits. For a two-parameter, read-only utility, nothing an agent needs to call it correctly is missing.

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 coverage is 100%, with both `data` and `format` documented and an enum for the five format values, so the baseline is 3. The description's note that `auto` detects gzip/zlib headers largely restates the schema's own wording and adds no new syntax or edge-case guidance (e.g. how ambiguous raw deflate is handled).

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?

States a specific verb and resource — decompressing base64 data — and enumerates the supported codecs (gzip, zlib/deflate, raw deflate, Brotli) with auto-detection. It explicitly names the sibling it is not (zlib-compress), so an agent can separate it from the compress counterpart without opening a schema.

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

Usage Guidelines4/5

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

There is an explicit 'Cuándo' block and a 'No para: comprimir ... (zlib-compress)' exclusion naming the alternative tool. The when-to-use sentence is a bit muddled ('to or from this encoding' applies to both directions, but this tool only decodes), which slightly weakens the routing signal.

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 toolsInspect
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