Skip to main content
Glama
prazedotid

UUID MCP Provider

by prazedotid

generateUuid

Generate timestamp-based UUID v7 identifiers for chronologically sortable unique IDs. Specify count parameter to create multiple identifiers at once.

Instructions

Generate one or more UUID v7s (timestamp-based). Specify count to get multiple.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNoHow many UUID v7 strings to generate (defaults to 1)

Implementation Reference

  • Handler logic for the generateUuid tool: extracts count from arguments (default 1), generates that many UUID v7s using uuidv7(), and returns them as newline-separated text content.
    if (request.params.name === "generateUuid") {
      // Pull from params.arguments per MCP spec
      const raw = request.params.arguments?.count;
      const count = typeof raw === "number" && raw >= 1 ? raw : 1;
    
      const uuids: string[] = [];
      for (let i = 0; i < count; i++) {
        uuids.push(uuidv7());
      }
    
      return {
        content: [
          {
            type: "text",
            text: uuids.join("\n")
          }
        ]
      };
    }
  • Input schema definition for generateUuid tool: object with optional 'count' integer property (min 1).
    inputSchema: {
      type: "object",
      properties: {
        count: {
          type: "integer",
          minimum: 1,
          description: "How many UUID v7 strings to generate (defaults to 1)"
        }
      },
      additionalProperties: false
    }
  • src/index.ts:14-37 (registration)
    Registers the generateUuid tool by handling ListToolsRequest and returning the tool metadata including name, description, and inputSchema.
    server.setRequestHandler(
      ListToolsRequestSchema,
      async () => {
        return {
          tools: [
            {
              name: "generateUuid",
              description: "Generate one or more UUID v7s (timestamp-based). Specify `count` to get multiple.",
              inputSchema: {
                type: "object",
                properties: {
                  count: {
                    type: "integer",
                    minimum: 1,
                    description: "How many UUID v7 strings to generate (defaults to 1)"
                  }
                },
                additionalProperties: false
              }
            }
          ]
        };
      }
    );
  • Imports the uuidv7 function used to generate UUIDs in the handler.
    import { v7 as uuidv7 } from "uuid";
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses that the tool generates UUID v7s (timestamp-based) and allows multiple generations via a count parameter, but it does not cover behavioral traits like rate limits, error handling, or output format. This adds basic context but leaves gaps in transparency.

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?

The description is two sentences, front-loaded with the core purpose and followed by parameter guidance. Every sentence earns its place without waste, making it efficient and well-structured for quick comprehension.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's low complexity (one optional parameter, no output schema, no annotations), the description is somewhat complete but lacks details on output format or behavioral constraints. It covers the basic operation but could be more informative for an agent to use the tool effectively without additional context.

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?

The schema description coverage is 100%, with the parameter 'count' fully documented in the input schema. The description adds minimal value by mentioning 'Specify `count` to get multiple,' which reinforces but does not expand beyond the schema. With high coverage, the baseline is 3, as the description does not significantly enhance parameter understanding.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: 'Generate one or more UUID v7s (timestamp-based).' It specifies the verb ('Generate'), resource ('UUID v7s'), and type ('timestamp-based'), but since there are no sibling tools, it cannot differentiate from alternatives. This makes it clear but not maximally specific.

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?

The description implies usage by stating 'Specify `count` to get multiple,' which suggests when to use the optional parameter. However, it lacks explicit guidance on when to use this tool versus alternatives or any exclusions, as there are no siblings. This provides some context but is not comprehensive.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/prazedotid/uuid-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server