Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

internet-exampleEmail

Generates an example email address using a person's first and last name as the base, with optional special characters.

Instructions

Generates an email address using an example mail provider 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-exampleEmail"
  }
}

Input Schema

NameRequiredDescriptionDefault
lastNameNoThe optional last name to use. If not specified, a random one 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

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; 'generates' does convey a side-effect-free, non-destructive operation. However, it does not state the actual domain produced, whether output is random or deterministic, or the address format, leaving meaningful behavioral details undisclosed.

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, though the repeated 'using ... using' phrasing is slightly clumsy and could be tightened without losing information.

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 simple three-optional-parameter generator with no output schema, the essentials are present and the schema covers parameter details. What is missing is the concrete shape of the result, such as the example domain and how the name is transformed, which an agent would want before relying on the output.

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 all three parameters, including the optionality of names and the special-characters flag, are already documented. The description adds only that the person's name is the base for the address, which is a marginal restatement rather than new meaning.

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 (generates) and resource (email address), plus a distinguishing qualifier: it uses an 'example mail provider' and derives from a person's name. This hints at the difference from the sibling internet-email tool without naming it explicitly, so an agent can infer the role but not confirm the routing.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: 'example mail provider' suggests synthetic/test addresses rather than real ones. There is no explicit when-to-use, when-not-to-use, or named alternative such as internet-email, so the agent must infer the choice.

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