Skip to main content
Glama
Sign In

Burs-IA Utils

by io.github.soyeladice-svg
OverviewDiscussionsAdmin

Generar ULID

ulid-generate
Read-only

Genera ULID: 26 caracteres Crockford Base32, marca de tiempo de 48 bits y 80 bits aleatorios; ordenables. Cuándo: hay que generar un identificador en este formato o leer los campos que lleva dentro. No para: validar un ULID y extraer su marca de tiempo y la parte aleatoria (ulid-decode). 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 ULIDs: 26-char Crockford Base32, 48-bit millisecond timestamp plus 80 random bits, sortable. 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: validating a ULID and extracting its timestamp (ulid-decode). Side effects: none (read-only, no network access, no stored state). [EN completo / full EN: inputSchema.description]

Input Schema

NameRequiredDescriptionDefault
seedNoOptional seed. With a seed the output is reproducible; without one, cryptographically random bytes are used (string; optional; up to 256 chars).
countNoHow many to generate (integer; optional; default 1; min 1; max 100).
timestamp_msNoUnix time in milliseconds to embed (default: now) (integer; optional; min 0; max 281474976710655).

Output Schema

NameRequiredDescriptionDefault
avisoNo
ulidsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / aviso
      Added value: +{
+  "type": [
+    "null",
+    "string"
+  ]
+}
  2. Changed1 schema field changed
    • addedInput schema / description
      Added value: +"EN: Generates ULIDs: 26-char Crockford Base32, 48-bit millisecond timestamp plus 80 random bits, sortable. 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: validating a ULID and extracting its timestamp (ulid-decode). 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."
  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 readOnlyHint=true, openWorldHint=false, idempotentHint=false, destructiveHint=false. The description still adds non-redundant context: no network, no stored state, non-deterministic unless both seed and timestamp_ms are given, and limits (input 64 KB, 1s per call, 1 MB result). The nondeterminism/reproducibility nuance is genuinely useful, though it partially restates idempotentHint=false.

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 format definition, then a structured When/Not for/Side effects/Non-determinism/Limits sequence. Dense but every clause is functional; the duplicated ES/EN block and the trailing pointer to inputSchema.description add some redundancy.

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?

Has an output schema, so return values needn't be explained, and annotations cover the safety profile. Coverage of scope, alternatives, determinism and size limits is thorough; minor deduction for the language duplication and slight overlap between the ES/EN paragraphs.

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 coverage is 100% and each parameter carries a full description including defaults and bounds, so the schema does the heavy lifting. The description echoes the seed/timestamp_ms reproducibility rule but adds no syntax or interaction detail beyond the schema — 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?

States a specific verb+resource (generates ULIDs), spells out the format (26-char Crockford Base32, 48-bit timestamp + 80 random bits, sortable), and explicitly distinguishes from ulid-decode. The agent can identify the tool and its output shape without opening the 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?

Provides explicit 'When:' (generating an identifier in this format or reading embedded fields) and 'Not for:' routing to ulid-decode for validation/extraction. This is the exact when/when-not/alternatives pattern.

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