Skip to main content
Glama

uuid_v7

Generate time-sortable RFC 9562 version 7 UUIDs (1-100 per call, optional timestamp) or validate/decode UUIDs to inspect version, variant, and embedded timestamps for v1/v7.

Instructions

RFC 9562 UUIDv7 generator (time-sortable, 1-100 per call, optional timestamp) and UUID validator/decoder (version, variant, embedded timestamp for v1/v7). Costs 0.001 USDC on Base per successful call (x402). Without a payment key this tool returns the 402 challenge.

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_v7"
  }
}

Input Schema

NameRequiredDescriptionDefault
uuidNoUUID to validate/decode instead
countNo1-100
timestampNoISO date for the time part

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A4.4/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full behavioral burden and does so: it discloses the pricing model and chain, the authentication prerequisite (payment key via x402), the exact failure behavior without a key (402 challenge), the per-call volume ceiling, and what the decode mode returns (version, variant, embedded timestamp for v1/v7). These are traits an agent could not infer from the schema alone.

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?

Three sentences, all load-bearing: capabilities first, then cost, then the failure mode. Nothing is repeated and the most decision-relevant facts (what it does, what it costs, what blocks it) are front-loaded.

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 3-parameter, zero-required tool with no output schema and no annotations, the description covers capabilities, limits, cost, and auth failure adequately. Minor gaps remain: it does not say what the default count is, nor what a validation result looks like for a non-v1/v7 UUID, nor error behavior beyond the 402 case.

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 every parameter is already documented in the schema, which sets the baseline at 3. The description echoes the 1-100 count range and the optional timestamp concept but adds no syntax, default, or format detail beyond what the schema fields already say.

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 states a specific verb and resource ('RFC 9562 UUIDv7 generator') and explicitly names the second mode ('UUID validator/decoder') with the fields it returns. An agent can tell immediately that this one tool covers both generation and validation 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 Guidelines4/5

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

It gives clear operating context: generation is 1-100 per call with an optional timestamp, decoding is the alternate mode, and the call costs 0.001 USDC on Base with a 402 challenge returned if no payment key is present. It does not explicitly state the condition that selects decode mode (passing a uuid) in the description body, and names no alternatives, so it stops short of full when/when-not guidance.

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