Skip to main content
Glama
laszlopere

mcp-bytesmith

id_generate

Create UUID, ULID, or nanoid identifiers with secure randomness. Select UUID version, set nanoid alphabet and size, or generate deterministic v5 IDs using a namespace and name.

Instructions

Generate one or more identifiers (UUID / ULID / nanoid).

All randomness is drawn from the OS CSPRNG (secrets). kind selects the family and which args apply. uuid honours version (default 4): v1 is time-based with a random node ID rather than the host MAC, v4 is 122 random bits, v5 is the SHA-1 of name within namespace (dns|url|oid|x500 or a UUID string) and so is deterministic — a count above 1 repeats it — and v7 is a 48-bit millisecond timestamp plus 74 random bits, which sorts by creation time. ulid is the same clock rendered as 26 Crockford base32 characters, also time-sortable. nanoid draws size (default 21) symbols from alphabet (default 64 url-safe chars). Returns {kind, ids} plus the resolved version (uuid) or size (nanoid). Example: id_generate("uuid", version=5, namespace="dns", name="example.com") -> ids ["cfbff0d1-9375-5685-968c-48ce8b15ae17"]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindYesIdentifier family: uuid (see `version`), ulid (time-sortable, 26 chars), or nanoid (custom `alphabet`/`size`).
nameNoUUID v5 name hashed within `namespace`, e.g. a hostname. Required with version=5.
sizeNoCharacter count for kind=nanoid; default None means 21.
countNoHow many IDs to generate, 1..1000; default 1.
versionNoUUID version for kind=uuid: 1 (time+random node), 4 (random), 5 (SHA-1 of namespace+name), 7 (time-sortable). Default 4.
alphabetNoSymbol set for kind=nanoid; default None uses the standard 64-char url-safe alphabet [A-Za-z0-9_-].
namespaceNoUUID v5 namespace: dns|url|oid|x500, or a UUID string. Required with version=5.
Behavior5/5

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

With no annotations, the description fully discloses key behaviors: randomness source (OS CSPRNG), determinism for v5, time-sortability for v7 and ulid, and return format. No destructive actions are implied, and all traits are accurately described.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

The description is well-structured, starting with a clear summary, then breaking down each kind systematically. No redundant sentences; each adds value. The example at the end is efficient and illustrative.

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?

Given the tool's complexity (7 parameters, multiple modes) and no output schema, the description covers all necessary context: parameter dependencies, return structure, and example usage. It is fully self-contained for correct invocation.

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

Parameters5/5

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

Schema coverage is 100%, but the description adds substantial meaning beyond schema descriptions, explaining how each parameter affects output (e.g., version effects, default sizes, required combinations). The example further clarifies parameter interplay.

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 clearly states the tool generates identifiers (UUID/ULID/nanoid) with specific verbs and resource types. It distinguishes between families and versions, providing a precise scope that differentiates from sibling tools like 'random' or 'hash'.

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?

While no explicit 'when to use' statement is given, the highly detailed description covers all variants and parameters, enabling an agent to infer appropriate contexts (e.g., deterministic IDs for v5, time-sortable for v7). No sibling tool duplicates this functionality, making usage unambiguous.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/laszlopere/mcp-bytesmith'

If you have feedback or need assistance with the MCP directory API, please join our Discord server