Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

image-avatarGitHub

Generates a random GitHub avatar image to provide placeholder profile pictures for testing, mockups, or demo data.

Instructions

Generates a random avatar from GitHub.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.2

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description has to carry the full behavioral burden. It does disclose that the output is random, which matters for reproducibility. However, it says nothing about what is returned (a URL, a data URI, or binary data), whether it needs network access or GitHub API auth, or whether rate limits apply.

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 definition is a single short sentence with the verb and the source front-loaded, and it has no filler. It is sized appropriately for a zero-parameter tool.

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, with no parameters and no nested objects, so the description is adequate for explaining the basic action. However, there is no output schema and no annotations, so the agent is left not knowing the return type or any operational constraints. Adding one clause about the output format would make the definition 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 tool takes zero parameters, so the schema leaves nothing to interpret, and the baseline for a parameterless tool is 4. The description correctly does not invent any inputs, which is consistent with the empty schema.

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 gives a specific verb and resource: it generates a random avatar, and it names GitHub as the source. That is clear enough to know what the tool produces. It does not differentiate itself from close siblings such as image-avatarLegacy or image-personPortrait, which also sound like image-generating tools.

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?

The description gives no guidance on when to use this tool rather than image-avatarLegacy or image-personPortrait, and no prerequisites or context of use. It only states the effect, so the agent must infer the use case itself.

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