Burs-IA Utils

UUID v5 (por nombre, SHA-1)

uuid-v5

Read-onlyIdempotent

Deriva el UUID versión 5 de un espacio de nombres y un nombre (SHA-1); las mismas entradas dan siempre el mismo UUID. Cuándo: hay que generar un identificador en este formato o leer los campos que lleva dentro. No para: derivar el UUID versión 3 de un espacio de nombres y un nombre (uuid-v3). 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 the RFC 9562 version-5 UUID of a namespace (dns, url, oid, x500 or any UUID) and a name, using SHA-1; the same inputs always give the same UUID. When: an identifier has to be generated in this format or its embedded fields decoded. Not for: deriving the RFC 9562 version-3 UUID of a namespace and a name, using MD5 (uuid-v3). 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
`name`	Yes	Name (string; required).
`namespace`	Yes	dns \| url \| oid \| x500 \| UUID (string; required; up to 36 chars).

Output Schema

Name	Required	Description	Default
`uuid`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 2, 2026
- addedInput schema / properties / name / examples
```
Added value: +[
+  "python.org"
+]
```
- addedInput schema / properties / namespace / examples
```
Added value: +[
+  "dns"
+]
```
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 readOnly, idempotent, openWorld=false and destructive=false, and the description restates those plus adds genuinely new operational limits (64 KB JSON input, 1 s per call, 1 MB result). The restatement of determinism/no-network is redundant with the annotations, which keeps it from 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.

Conciseness4/5

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

Front-loaded with the core verb and resource, then cleanly labeled When / Not for / Side effects / Deterministic / Limits. The cost is full bilingual duplication of the same content, which roughly doubles length without adding 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?

An output schema exists so return values need not be explained, and the description covers scope, alternatives, determinism, side effects and hard 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%, so both parameters are already documented, and the description's namespace enumeration (dns, url, oid, x500, any UUID) largely repeats the schema's own description. Baseline 3 is appropriate; it adds no new syntax or normalization detail 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: derive the RFC 9562 version-5 UUID of a namespace plus name using SHA-1, and also that it decodes embedded fields. It names the exact sibling it differs from (uuid-v3, MD5) so the agent can disambiguate without opening a 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 'When' clause (generate this identifier format or read its embedded fields) and an explicit 'Not for' clause routing to uuid-v3. Both the positive condition and the exclusion are stated.

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?