Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

person-suffix

Generate a random person suffix, such as Jr. or Sr., for fake names and sample person records in test data.

Instructions

Returns a random person suffix.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.2

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the behavioral burden. It does disclose the one genuinely behavioral trait — output is random/non-deterministic — which is useful. However it never states the return type or value domain (a plain string such as 'Jr.' versus a structured object), which matters because there is no output schema to fill that gap.

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 sentence with no filler and the purpose front-loaded. It is efficient but borders on under-specification — one short clause naming an example suffix would have cost almost nothing and removed the main ambiguity.

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 (no params, no nesting, no annotations), which lowers the bar. Still, with no output schema the description should say what comes back (a string) and roughly which values are possible, and it should note the distinction from person-prefix; neither is present.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters and the schema is empty with additionalProperties=false, so there is nothing for the description to explain. Baseline 4 applies; no parameter meaning is missing.

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 concrete verb and resource ('Returns a random ... suffix'), which is clearer than the hyphenated name alone; the word 'random' signals the generation aspect. It does not distinguish itself from the sibling person-prefix or clarify what a 'suffix' actually is (Jr., Sr., III, PhD), so an agent cannot fully disambiguate without opening the schema.

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 when-to-use guidance, no exclusions, and no mention of the obvious alternative (person-prefix) or how to combine with person-fullName. For a zero-parameter generator the correct usage is inferable, but the description provides nothing explicit.

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