Skip to main content
Glama
QianJue-CN

Random.org MCP Server

by QianJue-CN

generateUUIDs

Generate true random UUIDs (version 4) for applications requiring cryptographically secure identifiers. Specify quantity from 1 to 1,000.

Instructions

Generate true random UUIDs (version 4)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nYesNumber of UUIDs to generate (1-1,000)

Implementation Reference

  • MCP tool handler for generateUUIDs: calls RandomOrgClient.generateUUIDs and formats the API response as standardized MCP content block with JSON stringified result.
    private async handleGenerateUUIDs(args: any) {
      const result = await this.randomOrgClient.generateUUIDs(args);
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify({
              data: result.random.data,
              completionTime: result.random.completionTime,
              bitsUsed: result.bitsUsed,
              bitsLeft: result.bitsLeft,
              requestsLeft: result.requestsLeft,
              advisoryDelay: result.advisoryDelay,
            }, null, 2),
          },
        ],
      };
    }
  • src/server.ts:211-226 (registration)
    Tool registration in MCP server's ListTools response, defining name, description, and input JSON schema.
    {
      name: 'generateUUIDs',
      description: 'Generate true random UUIDs (version 4)',
      inputSchema: {
        type: 'object',
        properties: {
          n: {
            type: 'number',
            description: 'Number of UUIDs to generate (1-1,000)',
            minimum: 1,
            maximum: 1000,
          },
        },
        required: ['n'],
      },
    },
  • TypeScript interface defining input parameters for generateUUIDs (matches MCP inputSchema).
    export interface UUIDParams {
      n: number;
    }
  • TypeScript interface defining the output structure from Random.org API for UUID generation.
    export interface UUIDResult {
      random: {
        data: string[];
        completionTime: string;
      };
      bitsUsed: number;
      bitsLeft: number;
      requestsLeft: number;
      advisoryDelay: number;
    }
  • Core helper function in RandomOrgClient that performs input validation and makes the HTTP JSON-RPC request to Random.org's generateUUIDs API endpoint.
    async generateUUIDs(params: UUIDParams): Promise<UUIDResult> {
      this.validateUUIDParams(params);
      return this.makeRequest<UUIDResult>('generateUUIDs', params);
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool generates UUIDs but doesn't explain key behaviors such as randomness quality, performance characteristics, or error handling. This leaves significant gaps for a tool with potential complexity in random generation.

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 a single, efficient sentence with zero wasted words, clearly front-loading the core functionality. It's appropriately sized for a simple tool with one parameter.

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

Completeness2/5

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

Given no annotations and no output schema, the description is incomplete. It doesn't explain what the output looks like (e.g., format of returned UUIDs, array structure), nor does it cover behavioral aspects like rate limits or error cases, which are important for a generation tool.

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 input schema has 100% coverage, fully describing the single parameter 'n' with its type, description, and constraints. The description adds no additional parameter semantics beyond what the schema provides, so it meets the baseline score of 3 for high schema coverage.

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 clearly states the specific verb ('Generate') and resource ('true random UUIDs (version 4)'), distinguishing it from sibling tools like generateBlobs or generateStrings by specifying the exact type of data produced. It's precise and unambiguous about what the tool does.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives like generateStrings or generateIntegers, nor does it mention any prerequisites or exclusions. It lacks context for tool selection among siblings.

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/QianJue-CN/TRUERandomMCP'

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