Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

person-middleName

Generates a random middle name, optionally filtered by sex, to complete fake person records.

Instructions

Returns a random middle name.

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": "person-middleName"
  }
}

Input Schema

NameRequiredDescriptionDefault
sexNoThe optional sex to use. Can be either 'female' or 'male'.

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 behavioral burden. It establishes randomness but says nothing about return type, whether results repeat across calls, whether sex filters the pool, or what happens when no middle name exists for a given sex — all material for a generator tool with zero annotation coverage.

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. Its brevity is efficient rather than padded, though it shades into under-specification for a tool with a behavioral parameter.

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 — one optional enum parameter, no output schema, no nesting — so a single sentence is defensible. Still, an agent cannot tell from the definition whether sex actually filters output or how the random value is returned, leaving a real gap for an otherwise low-complexity tool.

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 single optional sex parameter is documented in the schema with an enum, so the baseline of 3 applies. The description adds no meaning beyond the schema — notably it never mentions sex or confirms that it constrains the generated name rather than being ignored.

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?

"Returns a random middle name" names a specific verb and resource, and the middle-name resource is distinguishable from siblings like person-firstName and person-lastName. It stops short of explicitly contrasting with person-fullName, which arguably already includes a middle name.

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 use this versus person-fullName or person-firstName, and no statement about the practical effect of supplying sex. The agent must infer that this is a standalone generator call.

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