Skip to main content
Glama

Generate UUID, ULID, nanoid or password values

uuid
Read-only

Identifiers and secrets from the Web Crypto random source: UUID v4 and v7, ULID, nanoid (size and alphabet), random passwords (length and character classes) and passphrases (words from the EFF large wordlist, CC BY 3.0 US), up to 100 per call. mode=parse validates a UUID or ULID and reports its version, variant and the time embedded in v1, v6, v7 and ULID. Nothing is stored. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "uuid"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNouuid4 (default), uuid7, ulid, nanoid, password or passphrase
modeNogenerate (default) or parse
sizeNonanoid length, 2 to 256, default 21
countNoHow many, 1 to 100, default 1
valueNomode parse: a UUID or ULID to check
wordsNopassphrase words, 3 to 10, default 6
lengthNopassword length, 8 to 128, default 20
classesNopassword classes: lower, upper, digits, symbols (comma-separated, default all)
alphabetNonanoid alphabet, 2 to 64 distinct characters (optional)
separatorNopassphrase separator, up to 3 characters, default -

Output Schema

NameRequiredDescriptionDefault
kindNo
modeNo
countNo
sourceNo
valuesNo
checkedAtNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered; the description adds genuinely new context — a hard cap of 100 results per call, an explicit 'Nothing is stored' statement, and pricing/billing behavior ($0.002 per successful call via x402 USDC, failed calls uncharged). Cost and failure-charging behavior are exactly the kind of operational detail annotations cannot convey. Return structure is not described, but an output schema exists, so that omission is acceptable rather than a gap.

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?

A single dense paragraph that front-loads the capability list and mode semantics before deferring pricing to the end. Every sentence carries information, though the payment-network enumeration ('USDC on Base, Solana and 10 more networks') is more detail than an agent needs to select or invoke the tool.

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?

For a 10-parameter generator with full schema coverage and an output schema, the description covers the essential facts: what is generated, the two modes, the 100-item ceiling, statelessness and cost. Edge cases such as alphabet validity or what happens on a malformed parse input are left to the schema, which is reasonable given the rich structured fields.

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 the schema already documents every parameter including defaults and ranges, so baseline is 3. The description adds only modest extra meaning — that nanoid takes a size and alphabet, passwords take length and character classes, and passphrases draw from the EFF large wordlist — mostly restating what the schema says, plus provenance (CC BY 3.0 US) that does not aid invocation.

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 opens with a specific verb class and enumerates the exact resources produced: UUID v4/v7, ULID, nanoid, passwords and passphrases from the Web Crypto random source, plus a parse/validate mode. An agent knows precisely what this tool returns without consulting the schema, and no sibling in the list overlaps with identifier generation.

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?

It clearly delineates the two operational modes (generate default vs. mode=parse validating a UUID/ULID and reporting version, variant and embedded timestamp) and states the per-call ceiling of 100 values. It does not name alternatives or exclusions, but the capability is self-contained and no obvious sibling competes, so the missing routing advice is low-cost.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources