Skip to main content
Glama
Sign In

Burs-IA Utils

by io.github.soyeladice-svg
OverviewDiscussionsAdmin

Clave de idempotencia

idempotency-key
Read-onlyIdempotent

Deriva una clave de idempotencia determinista de una solicitud (método, URL, cuerpo JSON canónico), para reutilizarla en reintentos. Cuándo: un flujo de agente necesita un resultado exacto y repetible para un paso auxiliar (tokens, costos, reintentos, fragmentos, ranking, limpieza de JSON). No para: derivar el UUID versión 5 de un espacio de nombres y un nombre (uuid-v5). 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: Derives a deterministic idempotency key from a request (method, URL, canonical JSON body, optional scope) as SHA-256 hex or a UUID-shaped string, so retries of the same request reuse the same key. When: an agent loop needs an exact, repeatable result for a bookkeeping step (tokens, costs, retries, chunking, ranking, JSON clean-up). [EN completo / full EN: inputSchema.description]

Input Schema

NameRequiredDescriptionDefault
urlYesURL or operation name (string; required; up to 8192 chars).
bodyNoJSON body (canonicalized) (any JSON value; optional; default null).
scopeNoExtra scope, e.g. user or payer ID (string; optional; default ""; up to 500 chars).
formatNoOutput format (optional; one of: hex, uuid; default "uuid").uuid
methodNoHTTP method (string; optional; default "POST"; up to 10 chars).POST

Output Schema

NameRequiredDescriptionDefault
keyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / url / examples
      Added value: +[
+  "https://api.x.co/orders"
+]
  2. Changed1 schema field changed
    • addedInput schema / description
      Added value: +"EN: Derives a deterministic idempotency key from a request (method, URL, canonical JSON body, optional scope) as SHA-256 hex or a UUID-shaped string, so retries of the same request reuse the same key. When: an agent loop needs an exact, repeatable result for a bookkeeping step (tokens, costs, retries, chunking, ranking, JSON clean-up). Not for: deriving the RFC 9562 version-5 UUID of a namespace (uuid-v5). 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.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint/openWorldHint=false, so 'sin red, sin estado guardado' and 'misma entrada da la misma salida' mostly restate structured data. The genuinely additive content is the operational limits (64 KB JSON input, 1 s per call, 1 MB output), which an agent cannot get from annotations and which affect batching decisions.

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?

Labeled sections (Cuándo / No para / Efectos / Determinista / Límites) make it skimmable and front-load the core definition. It is somewhat padded by ES→EN duplication and a dangling '[EN completo / full EN: inputSchema.description]' fragment that adds no 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?

A pure-function tool with an output schema, complete param docs, and a description that covers purpose, exclusions, determinism, side effects and size/time limits. Nothing an agent needs in order to call it correctly or decide against it is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description adds meaning beyond the schema by explaining that the body is canonicalized and that the format parameter yields either a SHA-256 hex digest or a UUID-shaped string. It does not, however, state how scope affects the derived key, which is the one parameter whose impact remains unexplained.

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 artifact ('Deriva una clave de idempotencia determinista de una solicitud') plus the exact inputs (method, URL, canonical JSON body, optional scope) and output encodings (SHA-256 hex or UUID-shaped). It also names the near-miss sibling uuid-v5, so an agent can separate the two 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?

Explicit 'Cuándo' clause enumerates the concrete scenarios (tokens, costs, retries, chunking, ranking, JSON clean-up) and an explicit 'No para' clause routes UUIDv5 derivation to the uuid-v5 sibling. Both when-to-use and when-not-to-use are stated, not implied.

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