Skip to main content
Glama

x420_id_generate

Generates UUID v4, time-ordered UUID v7, or ULID identifiers, 1–100 per call, for unique IDs in applications and systems.

Instructions

ID generator: Generates UUID v4, time-ordered UUID v7, or ULID identifiers (1–100 per call) from the runtime CSPRNG. Not professional, legal, insurance, engineering, medical, financial or tax advice. PAID: $0.01 USDC per call, settled on Base via x402 from the wallet in X420_MCP_WALLET_PRIVATE_KEY (real money). Returns: JSON: kind, count, generated_at, ids[] - the deliverable plus X420's signed receipt and the settlement transaction. Example input: {"kind":"ulid","count":"2"}.

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": "x420_id_generate"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNouuid4 (default), uuid7 or ulid
countNo1–100 (default 1)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the annotations it discloses the material behavior: a real $0.01 USDC charge per call settled on Base via x402 from a specific wallet env var, plus CSPRNG-sourced generation. It also describes the response as containing a signed receipt and settlement transaction, which the annotations and absent output schema would otherwise leave unknown.

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?

The generation, count, payment and return-value information is front-loaded and efficient, but the sentence "Not professional, legal, insurance, engineering, medical, financial or tax advice" carries no meaning for an ID generator and is pure boilerplate noise. One sentence does not earn its place.

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?

For a two-optional-parameter tool with no output schema, the description covers the generation modes, the count bounds, the monetary cost and payment path, and enumerates the return JSON keys (kind, count, generated_at, ids[]). An agent has everything needed to decide and call correctly.

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 description coverage is 100%, so both parameters already document valid values and defaults. The description only restates those ranges and adds a single example input, giving marginal meaning beyond the schema, so the baseline of 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?

The description names a specific verb and resource ("Generates UUID v4, time-ordered UUID v7, or ULID identifiers") and states the source of randomness and output volume. An agent can distinguish this from siblings like x420_hash_digest 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 Guidelines3/5

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

It implies when to use it (need for uuid4/uuid7/ulid identifiers, 1–100 per call) but never states when to choose uuid7 over uuid4 or ulid, nor any exclusions relative to siblings. The default behavior is only visible via the schema, not routed by the prose.

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