Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

image-url

Generate a random image URL with specified width and height for testing, placeholders, or mock data.

Instructions

Generates a random image url.

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

Input Schema

NameRequiredDescriptionDefault
widthNoThe width of the image.
heightNoThe height of the image.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.2

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. 'Random' hints at non-determinism, but nothing is said about the image source, whether the URL is stable or expires, whether network/auth is involved, rate limits, or what dimensions default to when width/height are omitted. For a zero-annotation tool this is a substantial 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 short sentence, front-loaded with the action and resource, with no filler or redundancy. It is efficient, though its brevity reflects missing information rather than tight editing.

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, has no required parameters, a fully documented schema, and no output schema to explain. Even so, the description leaves open what kind of random image is returned and how optional width/height affect output, which an agent would need to call it confidently.

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% and both parameters are documented as width and height, so the baseline is 3. The description adds no extra meaning such as units, allowed ranges, aspect-ratio behavior, or what happens when parameters are omitted (both are optional).

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 names a specific verb and resource: 'Generates a random image url.' An agent knows exactly what it produces. However, it does not distinguish this tool from sibling generators such as image-urlLoremFlickr, image-urlPicsumPhotos or image-urlPlaceholder, so the agent cannot tell which generator to pick from the description alone.

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 mention of when not to use it, and no reference to the multiple sibling image-url tools that would be the obvious alternatives. The agent must infer selection criteria from tool names alone.

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