Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

internet-mac

Generate a random MAC address with an optional ':', '-', or no separator for testing and mock data.

Instructions

Generates a random mac address.

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": "internet-mac"
  }
}

Input Schema

NameRequiredDescriptionDefault
separatorNoThe optional separator to use. Can be either `':'`, `'-'` or `''`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.2

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It does disclose the key behavioral trait that output is randomly generated (non-deterministic), but says nothing about the default format when separator is omitted, letter casing, or whether the result is a full 12-hex-digit address.

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 front-loaded sentence with no filler. It is efficient, though the brevity leaves room for one more clause about the default output format at minimal cost.

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?

For a zero-required-parameter generator with no output schema, the definition is minimally adequate: the purpose is obvious. However, an agent cannot predict the returned string's format (e.g., colon-separated lowercase by default), which is the one piece of information this tool's description should supply.

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% and the separator parameter is fully documented in the schema with its three allowed values. The description adds no additional meaning on top of that, so the baseline of 3 applies.

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?

"Generates a random mac address" names a specific verb and resource, so an agent can tell it apart from siblings like internet-ip or internet-ipv6 by subject matter. It stops short of differentiating within the internet-* generator family or describing the output shape, so it is clear but not fully distinguishing.

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 when-to-use guidance, no mention of alternatives such as internet-ip, and no statement of any preconditions. The agent must infer usage entirely from the name and the single optional parameter.

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