Burs-IA Utils

Generar UUID v4

uuid-v4

Read-only

Genera UUID versión 4 (RFC 9562) aleatorios. Con semilla, la salida es reproducible. Cuándo: hay que generar un identificador en este formato o leer los campos que lleva dentro. No para: generar UUID versión 7 ordenados por tiempo (uuid-v7). Efectos secundarios: ninguno (solo lectura, sin red, sin estado guardado). No determinista: aleatorio salvo que se dé seed. Límites: entrada JSON de hasta 64 KB, 1 s por llamada, resultado de hasta 1 MB.

EN: Generates random RFC 9562 version-4 UUIDs (122 random bits). A seed gives reproducible output for tests. When: an identifier has to be generated in this format or its embedded fields decoded. Not for: generating time-ordered version-7 UUIDs (uuid-v7). Side effects: none (read-only, no network access, no stored state). Not deterministic: random unless seed is given. Limits: JSON input up to 64 KB, 1 s per call, result up to 1 MB.

Input Schema

Name	Required	Description	Default
`seed`	No	Optional seed. With a seed the output is reproducible; without one, cryptographically random bytes are used (string; optional; up to 256 chars).
`count`	No	How many to generate (integer; optional; default 1; min 1; max 100).

Output Schema

Name	Required	Description	Default
`aviso`	No
`uuids`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 1, 2026
- addedOutput schema / properties / aviso
```
Added value: +{
+  "type": [
+    "null",
+    "string"
+  ]
+}
```
First observedNov 1, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, so the 'no side effects' sentence mostly restates structured data. The description does add genuinely new behavioral context: non-determinism unless a seed is supplied (consistent with idempotentHint=false) and concrete limits (64 KB input, 1 s per call, 1 MB result).

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?

Content is front-loaded and organized under explicit labels (When / Not for / Side effects / Limits), which makes it easy to scan. It is, however, fully duplicated in Spanish and English, roughly doubling length without adding information.

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 and limits, determinism, and the sibling alternative are all covered, so an agent has what it needs to call it correctly. The only soft spot is the phrase about 'reading embedded fields,' which overlaps the separate uuid-inspect tool and slightly blurs scope.

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 fully documented in the schema. The description reinforces the seed's reproducibility effect but says nothing about count, so it adds only marginal value over the structured fields — baseline 3 applies.

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?

The description names a specific verb and resource — 'Generates random RFC 9562 version-4 UUIDs (122 random bits)' — and explicitly frames the comparison against uuid-v7. An agent can distinguish it from the uuid-v3/v5/v7/inspect siblings without opening any 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?

It gives an explicit 'When:' (generate an identifier in this format or read its embedded fields) and an explicit 'Not for:' that names the alternative tool (uuid-v7, time-ordered). The condition that selects the sibling is stated outright, leaving nothing 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?