Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

internet-displayName

Generate a display name from a person's first and last name, with random values supplied for any missing parts. Use it to create realistic profile labels for fake data.

Instructions

Generates a display name 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-displayName"
  }
}

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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.2

TDQS

B3.1/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 it only hints at behavior via 'as base', which implies the output is a transformed rather than verbatim name. It says nothing about the shape of the produced string (concatenation, separators, appended digits), whether generation is deterministic, or whether the input is mutated or merely referenced; the random-fallback behavior is only visible in the schema.

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?

One short, front-loaded sentence with no filler or redundancy. The phrasing 'using the given person's name as base' is slightly awkward but not wasteful.

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?

There is no output schema and the description never characterizes the returned display name, which is the tool's entire product; an agent cannot predict whether the result is 'JohnDoe', 'j.doe', or 'JohnDoe42'. For a simple generator this gap is the main missing piece, and the description does not fill it.

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 both optional parameters are fully documented in the schema, including the random fallback when omitted. The description adds no further meaning about how firstName/lastName are combined into the display name, 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?

States a specific verb and resource: 'Generates a display name', and clarifies the derivation source ('using the given person's name as base'). It does not distinguish itself from near-siblings such as person-fullName or internet-userName, so an agent must infer the difference from the name alone.

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 by the purpose sentence – an agent can infer 'use when you need a display name derived from a person's name', but there is no explicit when/when-not guidance and no pointer to alternatives like person-fullName or person-firstName.

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