lazymac-mcp

fake_data_generator

Generate fake names, emails, addresses, and JSON data for testing purposes within the lazymac-mcp server environment.

Instructions

Generate fake names, emails, addresses, JSON for testing

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": "fake_data_generator"
  }
}

Input Schema

Name	Required	Description	Default
`params`	No	Free-form params object — passed as query string for GET, JSON body for POST

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Apr 15, 2026

TDQS

C2.9/5.0

Behavior2/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 of behavioral disclosure. It mentions what is generated but fails to describe key traits like output format details, rate limits, authentication needs, or whether data is persisted. This leaves significant gaps in understanding how the tool behaves.

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 extremely concise and front-loaded, listing key outputs in a single, efficient phrase without unnecessary words. Every element ('fake names, emails, addresses, JSON for testing') earns its place by specifying the tool's scope clearly.

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 the lack of annotations and output schema, the description is incomplete for a tool that generates data. It does not explain the return values, such as the structure of generated JSON or how outputs are formatted, leaving the agent with insufficient context to use the tool effectively.

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% description coverage, documenting a single 'params' object as free-form parameters. The description does not add any meaning beyond this, such as examples of common parameters or their effects. With high schema coverage, the baseline score of 3 is appropriate.

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 function with specific verbs ('Generate') and resources ('fake names, emails, addresses, JSON'), making its purpose immediately understandable. However, it does not differentiate from sibling tools, as none appear to be related to fake data generation, so a 5 is not warranted.

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, such as specifying scenarios for testing or mentioning other tools for similar purposes. It lacks explicit context or exclusions, leaving usage unclear beyond the basic function.

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