Skip to main content
Glama
Sign In
FauxGen MCP

FauxGen MCP

by LazyInvestor
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Generate MAC addresses

generate_mac

Create random MAC addresses for test data, device simulations, and fictional network identities, with configurable output count.

Instructions

Generate random MAC addresses.

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_mac"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/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 behavioral burden. It says 'random' but omits whether the output is unicast/locally-administered, what format (colon-separated hex, uppercase), whether duplicates are possible, or any rate limit — all relevant for a random generator.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single compact sentence with no filler; appropriately sized and front-loaded. It is economical, though bordering on under-specified rather than concise.

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?

The tool is simple and the description covers the core action, but with no annotations and no output schema the agent gets no sense of the return shape (single string vs. list when count > 1) or MAC format. Minimum viable, with gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the single parameter (count, default 1, max 50) is never mentioned. The description does not tell the agent that batching multiple addresses is possible or what the upper bound is, leaving a real gap.

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?

States a specific verb (Generate) and resource (random MAC addresses), which distinguishes it from siblings like generate_ip, generate_uuid, and generate_user_agent at a glance. It does not, however, add any scoping or output detail beyond the bare action.

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?

There is no indication of when to use this tool versus the many other generator siblings, nor any prerequisites or exclusions. For a family of near-identical generate_* tools, this omission is notable.

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