Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

image-dataUri

Generates random SVG data URIs, URL-encoded or Base64, with configurable color, width, and height for mockups and web assets.

Instructions

Generates a random data uri containing an URL-encoded SVG image or a Base64-encoded SVG image.

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

Input Schema

NameRequiredDescriptionDefault
typeNoThe type of the image to return.
colorNoThe color of the image. Must be a color supported by svg.
widthNoThe width of the image.
heightNoThe height of the image.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.2

TDQS

B3.2/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 the key behavioral trait: output is random and returned as either a URL-encoded or Base64-encoded data URI. It says nothing about what the generated SVG actually depicts, what happens with omitted color/width/height, or default values.

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?

One sentence, front-loaded with the verb and result, with zero filler. Slightly awkward phrasing ('an URL-encoded') but structurally sound.

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

Completeness4/5

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

For a four-parameter, all-optional, stateless image generator with a fully described schema and no output schema or annotations, the description covers the essentials: randomness and output encoding. The main omission is what the SVG content looks like, which matters for an image tool but is a minor gap at this complexity.

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%, so type, color, width and height are already documented, including the enum. The description adds no parameter-level meaning such as defaults, units, or valid ranges, so the baseline 3 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?

States a specific verb (Generates) and a specific resource (a random data URI containing an SVG image), with the two encoding variants named. It is distinguishable from sibling image-url tools because it clearly yields an inline data URI rather than a hosted URL, though it never says so explicitly.

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?

No when-to-use guidance at all: nothing explains when a data URI is preferable to the sibling image-url / image-urlPlaceholder tools, and no conditions or exclusions are stated. The agent must infer usage entirely from the one-line purpose.

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