Burs-IA Utils

Hash SHA-256

hash-sha256

Read-onlyIdempotent

Calcula el resumen SHA-256 (FIPS 180-4) en hex, base64 o base64url. 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 HMAC (hmac-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 SHA-256 digest (FIPS 180-4) of text, hex or base64 input, returned as hex, base64 or base64url. 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 HMAC (hmac-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.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, but the description adds real detail beyond them: no network access, no stored state, strict determinism, and hard limits (64 KB input, 1 s per call, 1 MB result). It stops short of describing error behavior when limits are exceeded, so not a 5.

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 content is well front-loaded — purpose first, then when/not-for, then effects and limits — but the entire block is duplicated verbatim in Spanish and English, roughly doubling length with zero added information for an agent reading either half.

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?

With an output schema available and annotations covering the safety profile, the description supplies everything else an agent needs: algorithm standard, input/output encodings, determinism, side effects, rate and size limits, and the sibling exclusion.

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 both enum parameters are already documented with defaults in the schema, so the baseline is 3. The description restates the supported input/output encodings but adds no syntax or edge-case meaning (e.g. how non-UTF-8 input is validated) beyond what the schema provides.

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 SHA-256 digest (FIPS 180-4) — with explicit coverage of input and output encodings. The 'Not for: computing the HMAC (hmac-sha256)' line separates it from the nearest sibling (hmac-sha256) and the wider hash-* family.

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 'When:' clause gives two concrete use cases (comparing content, matching a published checksum) and 'Not for:' names the alternative tool to use instead. An agent has a clear routing rule without inferring anything.

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?