Skip to main content
Glama
Sign In

Burs-IA Utils

by io.github.soyeladice-svg
OverviewDiscussionsAdmin

Decodificar hexadecimal

hex-decode
Read-onlyIdempotent

Decodifica hexadecimal a texto UTF-8 o base64. Cuándo: hay que convertir bytes o texto a esta codificación, o desde ella, con exactitud y sin adivinar. No para: codificar texto UTF-8 en hexadecimal, con separador opcional (hex-encode). 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: Decodes hexadecimal (case-insensitive; spaces, colons and 0x prefix ignored) to UTF-8 text or base64. When: bytes or text have to be converted to or from this encoding exactly, without guessing. Not for: encoding UTF-8 text (hex-encode). 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.

Input Schema

NameRequiredDescriptionDefault
hexYesHex string (string; required).
output_encodingNoOutput (optional; one of: utf8, base64; default "utf8").utf8

Output Schema

NameRequiredDescriptionDefault
dataNoany JSON value

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / hex / examples
      Added value: +[
+  "6869"
+]
  2. First observed

TDQS

A4.9/5.0
Behavior5/5

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

It adds significant operational context beyond the metadata, detailing side effects (none, read-only, no network access), deterministic nature, and crucial performance limits (64 KB input, 1 s per call, 1 MB result).

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

Conciseness5/5

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

The text is highly efficient. It front-loads the core functionality and organizes the supplementary information into logical categories (When, Not for, Side Effects, Limits), maximizing information density with minimal waste.

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?

It includes detailed behavioral constraints (performance limits, deterministic output, input size limits) which is essential for robust agent planning in data manipulation tasks.

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?

With 100% schema coverage, the baseline is high. The description still adds value by listing the allowed output encoding types and detailing input processing behavior (e.g., ignoring spaces and 0x prefixes).

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 states the tool decodes hexadecimal to either UTF-8 or base64. It provides specifics on how it handles input (case-insensitive, ignoring prefixes/separators) and explicitly differentiates itself from the encoding tool sibling.

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?

It provides precise 'When' (converting bytes/text exactly) and 'Not for' (encoding text), leaving no doubt about the appropriate use case or alternative sibling tool.

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