Skip to main content
Glama

X420 agent services

x420_id_generate

Read-onlyIdempotent

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. Price: $0.01 USDC per call (x402 on Base). This hosted tool does NOT pay and does NOT return the deliverable: it validates the input and returns payment instructions (pay_to, network, price and the x402 URL to pay at). GET the url; read PAYMENT-REQUIRED from the 402; retry with PAYMENT-SIGNATURE (x402 v2). Or run the local x420-mcp server with your own wallet key to pay automatically. Deliverable once paid: JSON: kind, count, generated_at, ids[].

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 observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already declare read-only/non-destructive/idempotent, but the description discloses the non-obvious behaviors the annotations cannot: the tool does not return IDs, it returns pay_to/network/price/x402 URL, costs $0.01 USDC on Base, and only yields JSON (kind, count, generated_at, ids[]) once paid. That is exactly the kind of context an agent would otherwise get wrong on first call.

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 purpose and payment mechanics are correctly front-loaded and dense, but 'Not professional, legal, insurance, engineering, medical, financial or tax advice' is boilerplate that does no work for a random-ID generator, and the x402 retry procedure is spelled out at a length that crowds out the parameter guidance.

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?

There is no output schema, and the description compensates by naming the exact deliverable fields (kind, count, generated_at, ids[]) along with price, network, and the payment handshake. For a two-optional-parameter tool, nothing an agent needs in order to call it correctly or interpret the result is missing.

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%, with the schema already stating 'uuid4 (default), uuid7 or ulid' and '1–100 (default 1)'. The description only adds the qualifier 'time-ordered' for uuid7 and the CSPRNG source; it does not mention that count is typed as a string, so it adds marginal meaning beyond the schema and the 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?

The opening states a specific verb and resource plus the exact variants produced: 'Generates UUID v4, time-ordered UUID v7, or ULID identifiers (1–100 per call) from the runtime CSPRNG.' That is enough to separate it from siblings like x420_hash_digest (hashing existing data) without opening a schema.

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 gives explicit operational guidance for the unusual hosted/payment mode: 'This hosted tool does NOT pay and does NOT return the deliverable', then the GET → read PAYMENT-REQUIRED → retry with PAYMENT-SIGNATURE sequence, plus the local-server alternative that pays automatically. It does not, however, advise when to prefer uuid4 vs uuid7 vs ulid, and gives no sibling-level exclusions.

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