Burs-IA Utils

Generar UUID v7 (ordenado por tiempo)

uuid-v7

Read-only

Genera UUID versión 7 (RFC 9562), ordenables por tiempo: marca de 48 bits en ms más bits aleatorios. Cuándo: hay que generar un identificador en este formato o leer los campos que lleva dentro. No para: generar UUID versión 4 (uuid-v4). Efectos secundarios: ninguno (solo lectura, sin red, sin estado guardado). No determinista: aleatorio y según el reloj salvo que se den seed y timestamp_ms. Límites: entrada JSON de hasta 64 KB, 1 s por llamada, resultado de hasta 1 MB.

EN: Generates RFC 9562 version-7 UUIDs: 48-bit Unix millisecond timestamp plus random bits, so they sort by creation time. Output is reproducible only when both seed and timestamp_ms are given; otherwise the clock and/or secure randomness are used. When: an identifier has to be generated in this format or its embedded fields decoded. Not for: generating random RFC 9562 version-4 UUIDs (uuid-v4). Side effects: none (read-only, no network access, no stored state). [EN completo / full EN: inputSchema.description]

Input Schema

Name	Required	Description
`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).
`timestamp_ms`	No	Unix time in milliseconds to embed (default: now) (integer; optional; min 0; max 281474976710655).

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"
+  ]
+}
```

Changed1 schema field changedNov 1, 2026

addedInput schema / description

Added value: +"EN: Generates RFC 9562 version-7 UUIDs: 48-bit Unix millisecond timestamp plus random bits, so they sort by creation time. Output is reproducible only when both seed and timestamp_ms are given; otherwise the clock and/or secure randomness are used. When: an identifier has to be generated in this format or its embedded fields decoded. Not for: generating random RFC 9562 version-4 UUIDs (uuid-v4). Side effects: none (read-only, no network access, no stored state). Not deterministic: random and clock unless seed and timestamp_ms are given. Limits: JSON input up to 64 KB, 1 s per call, result up to 1 MB."

First observedNov 1, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already declare readOnly/openWorld/idempotent/destructive flags, and the description goes well beyond them: it discloses non-determinism and the exact condition for reproducibility (both seed and timestamp_ms), confirms no network or stored state, and states operational 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.

Conciseness3/5

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

Content is front-loaded and the When/Not-for/Effects/Limits structure is easy to scan, but the text is published twice (Spanish block plus a near-duplicate English block) and ends with a stray artifact '[EN completo / full EN: inputSchema.description]' 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?

With an output schema present, return values need not be described; annotations carry the safety profile and the description covers determinism, limits, and usage boundaries. Nothing needed 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.

Parameters4/5

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

Schema coverage is 100%, so the schema alone would justify a 3. The description adds real value by clarifying that reproducibility requires both seed and timestamp_ms together, which the per-parameter schema text only states for seed individually.

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 ('Genera UUID versión 7 (RFC 9562)') and adds the defining property (time-sortable: 48-bit ms timestamp + random bits). An agent can distinguish it from uuid-v4 and uuid-v5 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit 'Cuándo' and 'No para: generar UUID versión 4 (uuid-v4)', naming an alternative and the condition that selects it. However, 'leer los campos que lleva dentro' overlaps with the uuid-inspect sibling, which is not addressed, leaving a decoding ambiguity unresolved.

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?