Skip to main content
Glama
Sign In
FauxGen MCP

FauxGen MCP

by LazyInvestor
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Generate UUIDs

generate_uuid

Generate one or more UUID v4 values for test data. This FauxGen MCP tool creates unique identifiers for seeding fictional records and mocks.

Instructions

Generate one or more UUID v4 values.

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

NameRequiredDescriptionDefault
countNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
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 does convey the important behavioral trait that values are v4 (random, non-sequential) and that more than one can be returned, but it omits the schema's cap of 50, says nothing about uniqueness guarantees, and does not describe the return format.

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?

One sentence, front-loaded with the verb and resource, with zero filler. Every word earns its place for a tool this simple.

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 stateless generator with one optional parameter and no output schema, the description plus schema is nearly sufficient. The remaining gap is the shape of the return value (single string vs array when count > 1), which the agent must infer.

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 0% and the single 'count' parameter has no description in the schema, so the description must compensate. 'One or more' partially documents count's semantics, but the default of 1 and the maximum of 50 are left entirely to the schema.

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?

States a specific verb (Generate) and resource (UUID v4 values), which cleanly distinguishes it from every sibling generator (email, name, address, etc.). The version qualifier 'v4' adds precision an agent can act on.

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?

No guidance on when to use this tool versus the sibling generators or versus other ID mechanisms; usage is only implied by the name. For a trivial generator this is tolerable, but nothing in the text routes the agent.

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

Deploy Server

Other Tools