Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

person-prefix

Generate a random title prefix, optionally filtered by female or male sex, to build realistic fake personal data.

Instructions

Returns a random person prefix.

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

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

B3.1/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. It discloses that output is random, but says nothing about whether the sex parameter filters results, what values are possible, whether the call is stateless/read-only, or what form the return takes.

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?

The description is a single front-loaded sentence with no wasted wording. It is appropriately sized for a simple generator, even though it omits useful detail.

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 one-parameter generator, the schema fully documents the optional sex filter and no output schema exists. However, the description leaves 'prefix' undefined and does not explain how sex affects the returned prefix, so it is only minimally complete.

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?

The single optional sex parameter has 100% schema description coverage, including an enum of 'female' and 'male'. The description adds no meaning beyond that, so the baseline of 3 is appropriate.

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 states a specific verb ('Returns') and resource ('person prefix'), and 'random' adds scope beyond the tool name. It does not explicitly distinguish this from sibling generators such as person-suffix or person-fullName, nor does it define what a 'prefix' is.

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 tool versus alternatives like person-suffix or person-fullName. The optional sex parameter is left entirely to the schema, with no indication of when or why an agent should supply it.

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