Burs-IA Utils

Hash SHA-224

hash-sha224

Read-onlyIdempotent

Calcula el resumen SHA-224 (FIPS 180-4). 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 SHA-224 digest (FIPS 180-4) of text, hex or base64 input. 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.6/5.0

Behavior5/5

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

Annotations already declare readOnly/openWorld=false/idempotent/destructive=false, and the description still adds value beyond them: determinism, absence of network or stored state, and concrete limits (64 KB JSON input, 1 s per call, 1 MB result). That is exactly the residual context annotations cannot express.

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

Conciseness4/5

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

Well front-loaded with labeled sections (When / Not for / Side effects / Limits), so it scans quickly. It loses a little to full duplication in Spanish and English, which doubles length without adding information for a single reader.

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?

Output schema covers the return value, annotations cover the safety profile, and the description covers determinism and operational limits — nothing an agent needs to call this 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 enums fully documented, so the schema carries the parameter burden. The description only restates that input may be text, hex or base64 — matching the existing enum — without extra format or edge-case guidance.

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-224 digest, FIPS 180-4) with explicit input types, and explicitly distinguishes itself from the nearest sibling hash-sha256. An agent can select it without opening the 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?

Uses explicit 'When:' (exact digest of given text/bytes, checksum comparison) and 'Not for:' (SHA-256 → hash-sha256) clauses, naming the alternative and the condition that selects it.

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?