Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

internet-userName

Generates a username from a given first and last name, or picks random names when none are provided. Useful for creating test accounts and mock user profiles.

Instructions

Generates a username using the given person's name as base. (Deprecated: Use faker.internet.username() instead.)

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

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.4/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 burden. Beyond the deprecation notice, it says nothing about the nature of the output (whether numbers/separators are appended, randomness, format), nor about determinism or collision handling for a generated identifier.

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

Conciseness5/5

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

Two short sentences with the core action front-loaded and the deprecation caveat immediately after; no filler wording.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a trivial two-optional-parameter generator with fully described schema and no output schema, the description covers purpose and deprecation status. The only meaningful gap is what the returned username string looks like.

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 parameters are documented as optional with random fallback, so the baseline is 3. The description adds only slightly by clarifying the name is used as a base for a derived username rather than returned directly.

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 username using the given person's name as base." The phrase "using the given person's name as base" distinguishes it from name generators like person-firstName or internet-displayName, though it never explicitly contrasts with them.

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?

The deprecation note tells the agent not to use this tool and points to faker.internet.username() instead, which is real usage guidance. However, it gives no guidance on when to prefer this over sibling generation tools or whether the replacement is available in this MCP server.

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