Skip to main content
Glama
Sign In

Burs-IA Utils

by io.github.soyeladice-svg
OverviewDiscussionsAdmin

Keccak-256 (Ethereum)

hash-keccak256
Read-onlyIdempotent

Calcula el Keccak-256 con el relleno original de Keccak, como en Ethereum (direcciones, selectores). Distinto de SHA3-256. 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 Keccak-256 with original Keccak padding, as used by Ethereum for addresses, function selectors and event topics. Differs from SHA3-256. 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. [EN completo / full EN: inputSchema.description]

Input Schema

NameRequiredDescriptionDefault
dataYesInput data (string; required).
input_encodingNoHow `data` is encoded (optional; one of: utf8, hex, base64; default "utf8").utf8
output_encodingNoOutput encoding of the digest (optional; one of: hex, base64, base64url; default "hex").hex

Output Schema

NameRequiredDescriptionDefault
digestNo
encodingNo
algorithmNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / data / examples
      Added value: +[
+  ""
+]
  2. Changed1 schema field changed
    • addedInput schema / description
      Added value: +"EN: Computes the Keccak-256 with original Keccak padding, as used by Ethereum for addresses, function selectors and event topics. Differs from SHA3-256. 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."
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, yet the description still adds real value: determinism, no network, no stored state, and concrete limits (1 s per call, 1 MB result). The limit statement is partially undermined by 'entrada JSON de hasta 64 KB' while the schema allows maxLength 1048576, an internal inconsistency that costs a point.

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?

The body is front-loaded and clearly labeled (Cuándo / No para / Efectos secundarios / Determinista / Límites), with no filler sentences. The trailing '[EN completo / full EN: inputSchema.description]' pointer is meta-noise that slightly dilutes an otherwise tight definition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need no explanation, and the description covers purpose, selection criteria, determinism and limits. The only gap is the conflicting input-size figure (64 KB in prose vs 1 MB in schema), which an agent could misread as a hard cap.

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 enums (input_encoding, output_encoding) are documented in the schema, so the baseline is 3. The description only hints at 'texto o unos bytes' to imply encoding choice and adds no syntax or format guidance beyond the schema.

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 ('Calcula el Keccak-256 con el relleno original de Keccak') and immediately scopes it to the Ethereum use case (addresses, function selectors, event topics). It also explicitly disambiguates from the most confusable sibling, SHA3-256, naming hash-sha3-256.

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 'Cuándo' clause (need an exact digest of text/bytes, compare content, match a published checksum) and an explicit 'No para' clause routing to hash-sha3-256. This is the when/when-not/alternative pattern in full.

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