Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

image-avatarLegacy

Generates a random avatar from a deprecated IPFS URL; the links no longer work, so use avatar() instead.

Instructions

Generates a random avatar from https://cloudflare-ipfs.com/ipfs/Qmd3W5DuhgHirLHGVixi6V76LhCkZUz6pnFt5AJBiyvHye/avatar. (Deprecated: The links are no longer working. Use avatar() instead.)

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.2

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does well: it discloses the backing URL and, critically, that returned links are broken. It doesn't describe the image format or size of the generated avatar, but for a zero-parameter random-image tool the deprecation notice is the behavior that matters most.

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 sentences, front-loaded with the action and immediately followed by the deprecation warning and alternative. The long IPFS URL is the only bulk, and it is functional information rather than filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter tool with no output schema, the description covers what it returns, where the content comes from, that the output is currently broken, and what to use instead. Nothing an agent needs in order to decide whether to call it is missing.

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 no parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description correctly implies the tool is argument-free by describing a fully random generation.

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?

States a specific verb and resource ('Generates a random avatar') and identifies the exact source URL, so the agent knows precisely what it produces. It also flags itself as legacy versus a replacement, though the replacement is named 'avatar()' while the actual sibling is 'image-avatar', which introduces minor ambiguity about which tool to switch to.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says the tool is deprecated because the links no longer work and directs the agent to an alternative, which is strong when-not-to-use guidance. The only gap is the slightly mismatched alternative name, so the agent must still map 'avatar()' onto the 'image-avatar' sibling 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