Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

color-rgb

Generates an RGB color in hex, CSS, binary, or decimal format, with optional casing, prefix, and alpha values for mock data and UI testing.

Instructions

Returns an RGB color.

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": "color-rgb"
  }
}

Input Schema

NameRequiredDescriptionDefault
casingNoLetter type case of the generated hex color.
formatNoFormat of generated RGB color.
prefixNoPrefix of the generated hex color. Only applied when 'hex' format is used.
includeAlphaNoAdds an alpha value to the color.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.2

TDQS

C2.3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden and does not meet it. It does not disclose that the tool generates a color, whether randomness is involved, what the default format is, or how the format/casing/prefix parameters affect output.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence is compact with no wasted words, but it is an under-specified fragment that mainly repeats the tool name. It is front-loaded but does not provide enough substance to be considered well-structured.

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

Completeness2/5

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

For a tool with four optional parameters controlling format, casing, prefix, and alpha, plus no output schema or annotations, one short sentence is inadequate. An agent cannot tell what the return value looks like or how these parameters interact from the description alone.

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 the input schema already documents casing, format, prefix, and includeAlpha thoroughly. The description adds no parameter meaning beyond the schema, which is the baseline expectation when schema coverage is high.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Returns an RGB color" essentially restates the tool name color-rgb rather than specifying a distinct verb and resource scope. It does not clarify whether this generates a color, converts one, or looks one up, and it does not distinguish the tool from siblings such as color-hsl or color-cmyk.

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 guidance on when to use this tool versus the many sibling color tools, nor any mention of prerequisites or exclusions. The reader is left to infer usage entirely from the name.

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