Burs-IA Utils

Hash MD5

hash-md5

Read-onlyIdempotent

Calcula el resumen MD5. No es criptográficamente seguro; solo para checksums o compatibilidad. Cuándo: se necesita el resumen exacto de un texto o de unos bytes dados, p. ej. para comparar contenido o cotejar un checksum publicado. No para: calcular el resumen SHA-256 (hash-sha256). 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: Computes the MD5 digest (128-bit). Not collision resistant: suitable only for checksums, cache keys or legacy interop, never for security. When: an exact digest of given text or bytes is needed, e.g. to compare content or match a published checksum. Not for: computing the SHA-256 digest (hash-sha256). 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

Name	Required	Description	Default
`data`	Yes	Input data (string; required).
`input_encoding`	No	How `data` is encoded (optional; one of: utf8, hex, base64; default "utf8").	utf8
`output_encoding`	No	Output encoding of the digest (optional; one of: hex, base64, base64url; default "hex").	hex

Output Schema

Name	Required	Description	Default
`digest`	No
`encoding`	No
`algorithm`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 2, 2026
- addedInput schema / properties / data / examples
```
Added value: +[
+  "abc"
+]
```
First observedNov 1, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, but the description adds genuinely new context: determinism, no network or stored state, the non-collision-resistant caveat, and concrete limits (64 KB JSON input, 1 s per call, 1 MB result). Those operational limits are not in the annotations or schema.

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?

Well-structured with labelled When / Not for / Side effects / Deterministic / Limits sections and the purpose front-loaded. However, the entire content is duplicated verbatim in Spanish and English, roughly doubling length for no additional information.

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?

For a small pure-function hashing tool with an output schema and full annotation coverage, the description supplies everything an agent needs: purpose, exclusions, determinism, safety caveat, and size/time limits. Return format need not be explained since an output schema exists.

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% with enum values and defaults fully documented, so the schema carries parameter meaning. The description only loosely gestures at 'text or bytes', which hints at input_encoding without naming the utf8/hex/base64 options or the output_encoding choices; baseline 3 applies.

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 ('Computes the MD5 digest (128-bit)') and immediately qualifies the algorithm's security properties. It explicitly distinguishes itself from the sibling hash-sha256, so an agent can pick between them without opening either 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?

Provides an explicit 'When:' clause (exact digest of given text/bytes, comparing content, matching a published checksum) and an explicit 'Not for:' clause naming the alternative hash-sha256. It also scopes the tool to checksums/cache keys/legacy interop and excludes security use.

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?