Burs-IA Utils

Hash SHA3-224

hash-sha3-224

Read-onlyIdempotent

Calcula el resumen SHA3-224 (FIPS 202) de texto, hex o base64. 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 SHA3-256 (hash-sha3-256). 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 SHA3-224 digest (FIPS 202) 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 SHA3-256 digest (hash-sha3-256). 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.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint=false and idempotentHint, so part of the side-effect statement is redundant. The description still adds genuinely new context: determinism guarantee, 64 KB JSON input cap, 1 s per-call limit and 1 MB result cap, which matter for callers handling large payloads.

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 structured and front-loaded with the core action, then 'When/Not for/Side effects/Limits' in a predictable order. The full Spanish/English duplication roughly doubles length for a simple hashing utility, which is some waste but the paragraphs remain scannable.

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 single-purpose hashing tool with annotations, full schema coverage and an output schema, the description covers purpose, routing, side effects and resource limits. Nothing an agent needs to invoke 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 description coverage is 100% and both enum parameters are documented in the schema, so baseline is 3. The description only echoes that input may be text, hex or base64 and says nothing about output_encoding choices (hex/base64/base64url) beyond what the schema already lists.

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 SHA3-224 digest per FIPS 202) plus the accepted input forms, and explicitly excludes the nearest sibling hash-sha3-256. 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?

Contains an explicit 'When' clause with concrete scenarios (comparing content, matching a published checksum) and an explicit 'Not for' clause naming the alternative tool. Nothing is left to inference.

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?