UUID AI MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generate_uuidC | Generate one or more UUIDs. Supports versions 1, 3, 4, and 5. |
| parse_uuidB | Parse and validate a UUID string, extracting all components. |
| generate_ulidC | Generate ULID(s) - Universally Unique Lexicographically Sortable Identifiers. |
| generate_nanoidC | Generate NanoID(s) - compact URL-friendly unique identifiers. |
| batch_generateB | Batch generate identifiers of a specified type. Efficient for bulk operations. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool targets a distinct operation (batch generate, specific generate for each ID type, parse UUID) with no overlapping purposes.
Most tools follow a verb_noun pattern (e.g., generate_uuid, parse_uuid), but batch_generate deviates slightly by not specifying the ID type in its name.
Five tools is well-scoped for a focused server on identifier generation and parsing, covering the core use cases without bloat.
Generation covers UUID, ULID, and NanoID, but parsing is only available for UUID, leaving a slight asymmetry. No other obvious gaps.