Underground Cultural District MCP Server

generate-uuid

Generate UUID v4 identifiers for your applications. Returns 1–100 unique UUIDs, one per line.

Instructions

Generate UUID v4 identifiers. Returns 1–100 UUIDs, one per line.

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": "generate-uuid"
  }
}

Input Schema

Name	Required	Description	Default
`count`	No	How many UUIDs (1–100, default 1)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv4.1.0Apr 17, 2026

TDQS

A3.8/5.0

Behavior3/5

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

No annotations provided. The description only states that it generates UUIDs and returns them one per line. It lacks disclosure of side effects, prerequisites, or limits beyond the count constraint mentioned in parameters.

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, front-loaded sentence with no wasted words. It is concise and informative.

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 simple tool with one parameter and no output schema or annotations, the description covers the essential behavior (generates UUIDs, returns them one per line). It could mention that output is plain text, but not critical.

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 a clear parameter description. The tool description does not add additional meaning beyond what the schema provides, so baseline 3 is appropriate.

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 verb 'Generate', the resource 'UUID v4 identifiers', and the output format 'Returns 1–100 UUIDs, one per line'. It is specific and distinguishes from siblings.

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 for generating UUIDs but does not explicitly state when to use it or provide alternatives. It gives no when-not or context for when other tools might be preferable.

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