Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

person-bio

Generates a random short biography for testing, mock profiles, and sample content so you can populate fake person records without writing text yourself.

Instructions

Returns a random short biography.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.2

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations at all, the description carries the full behavioral burden, and it does disclose two useful traits: output is non-deterministic ("random") and truncated ("short"). It does not say whether the biography is synthetic/placeholder data, whether it corresponds to an actual person entity, or what fields the biography string contains.

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?

A single nine-word sentence with the key qualifiers (random, short) front-loaded and no filler. Nothing could be removed without losing information.

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 parameterless generator the description is close to complete, but with no output schema the agent still does not know the shape or length of the returned biography string (name+age+occupation sentence vs. free prose, language, approximate size). One additional clause describing the return value would make it fully complete.

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 input schema has zero properties and the tool takes no arguments, so there is no parameter meaning to add; baseline applies. Nothing in the description contradicts or obscures the empty parameter surface.

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 short biography" names a specific verb (returns) and resource (a short biography) with an explicit randomness qualifier, so an agent knows exactly what data it yields. It does not need to differentiate from the listed siblings, which generate entirely different data types, but it also makes no attempt to distinguish itself from any hypothetical broader bio generator.

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?

There is no explicit when-to-use or when-not-to-use guidance, only the implicit cue that this is a generator of fictional/sample bio text rather than real person data. For a zero-parameter tool whose purpose is self-evident from the name, that implied usage is adequate but nothing more.

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