Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

image-urlPicsumPhotos

Generate random placeholder image URLs from Picsum Photos with configurable width, height, blur, and grayscale settings for testing and mock data.

Instructions

Generates a random image url provided via https://picsum.photos.

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

Input Schema

NameRequiredDescriptionDefault
blurNoWhether the image should be blurred. 0 disables the blur.
widthNoThe width of the image.
heightNoThe height of the image.
grayscaleNoWhether the image should be grayscale.

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 burden. It does usefully imply the tool returns a URL string rather than image bytes, but it says nothing about whether the returned URL is stable or random per call, how the picture is chosen, rate limits, or what happens if picsum.photos is unreachable — meaningful gaps for a network-backed tool with zero annotation coverage.

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 with no wasted clauses, and the resource and provider are front-loaded. The phrasing 'provided via https://picsum.photos' is slightly awkward but not harmful.

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 (4 optional params, no nesting), but with no annotations and no output schema the description should state what is returned — a plain URL string — and note that dimensions default when omitted. As written, an agent knows what the tool does but not the shape of its result.

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 every property (blur enum, width, height, grayscale) is documented in the schema itself. The description adds nothing about parameter meaning, so the baseline 3 for fully-covered schemas applies.

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?

A specific verb+resource ('Generates a random image url') plus the upstream provider domain (picsum.photos), which tells an agent this is the Picsum-backed variant among the image-url siblings. It stops short of explicitly contrasting with image-urlLoremFlickr or image-urlPlaceholder, so sibling differentiation is only implicit.

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 when-to-use context: no statement of when to pick Picsum over the other image-url providers, no prerequisites, and no note that all four parameters are optional or that defaults apply. Only the bare domain hints at the use case.

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