Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

image-personPortrait

Generates a random square portrait of a fictional person, letting you create avatar images with selectable sex and size.

Instructions

Generates a random square portrait (avatar) of a person. These are static images of fictional people created by an AI, Stable Diffusion 3.

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": "image-personPortrait"
  }
}

Input Schema

NameRequiredDescriptionDefault
sexNoThe sex of the person for the avatar. Can be 'female' or 'male'.
sizeNoThe size of the image. Can be 512, 256, 128, 64 or 32.

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?

With no annotations, the description carries the full burden, and it does disclose meaningful traits: output is random/non-deterministic, images are square, static, and depict fictional AI-generated people (Stable Diffusion 3). It omits what is returned (URL vs binary), whether results are cached, and any rate or cost considerations, which matters for an image-generation tool.

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, front-loaded with the core action, with no redundant or filler wording. The second sentence earns its place by establishing that the subjects are fictional and AI-generated.

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 two-optional-parameter tool with a fully documented schema, the description covers purpose and content nature adequately. However, with no output schema and no annotations, it should say what the caller receives (image URL, data URI, or bytes) and whether the random result is stable across calls.

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 description coverage is 100% with both parameters enumerated and documented, so the baseline is 3. The description adds only marginal meaning beyond the schema — 'square' implies the aspect ratio is fixed regardless of size, and 'random' implies parameters do not control identity — but gives no guidance on defaults or how size affects output.

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 and resource: generating a random square portrait/avatar of a person, and clarifies these are AI-generated fictional people. It is clear on its own, but it never distinguishes itself from the several avatar siblings (image-avatar, image-avatarGitHub, image-avatarLegacy), so an agent cannot tell from the text which avatar tool to pick.

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 or when-not-to-use guidance, and no mention of the alternative avatar tools despite a crowded sibling set. The word 'random' is the only implicit signal about how this differs from deterministic avatar generators, which is not enough to route an agent.

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