Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

internet-email

Generate an email address from a person's name, with optional first and last names, mail provider, and special-character settings for realistic fake contact data.

Instructions

Generates an email address using the given person's name as base.

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

Input Schema

NameRequiredDescriptionDefault
lastNameNoThe optional last name to use. If not specified, a random one will be chosen.
providerNoThe mail provider domain to use. If not specified, a random free mail provider will be chosen.
firstNameNoThe optional first name to use. If not specified, a random one will be chosen.
allowSpecialCharactersNoWhether special characters such as `.!#$%&'*+-/=?^_`{|}~` should be included in the email address.

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?

No annotations are supplied, so the description carries the full disclosure burden and does not meet it. It never says the result is randomized/fake, that unspecified fields are filled with random values, whether the domain is guaranteed to be a safe example domain, or what the returned string looks like. For a generator tool whose output varies between calls, the absence of any determinism or reproducibility note is a real gap.

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 or redundancy. It is efficient, though so terse that brevity shades into under-specification rather than polished concision.

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, all four parameters are fully described in the schema, and there is no output schema or annotation set to reconcile. Still, an agent would benefit from knowing that output is non-deterministic and what form the email takes, which the description omits entirely.

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 description coverage is 100%, so firstName, lastName, provider, and allowSpecialCharacters are already fully documented inline. The description adds only the notion of a name 'base' and says nothing about provider or special-character handling, so it neither compensates nor detracts. Baseline 3 applies when the schema does the work.

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 gives a specific verb and resource: 'Generates an email address using the given person's name as base.' An agent can immediately tell this produces a synthetic email address. It does not, however, distinguish itself from a similarly purposed sibling (e.g. internet-exampleEmail or internet-username), so it stops short of a 5.

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 guidance on when to choose this over internet-exampleEmail or internet-userName, and no statement of context such as 'use for test fixture data'. The only hint at behavior is the phrase 'as base', which does not tell the agent what happens when no name is supplied.

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