Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

internet-color

Generates a random CSS hex color code from an aesthetically pleasing palette, with optional red, green, and blue base values for customized results.

Instructions

Generates a random css hex color code in aesthetically pleasing color palette. (Deprecated: Please use faker.color.rgb() or any of the other color methods 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": "internet-color"
  }
}

Input Schema

NameRequiredDescriptionDefault
redBaseNoThe optional base red in range between `0` and `255`.
blueBaseNoThe optional base blue in range between `0` and `255`.
greenBaseNoThe optional base green in range between `0` and `255`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.2

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the burden. It discloses that output is random and constrained to a pleasant palette, but says nothing about whether results are seedable/repeatable, what the exact return value looks like, or how the optional base parameters bias the result. That leaves meaningful behavioral gaps for a no-annotation tool.

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?

Two compact sentences with no filler, and the core purpose is front-loaded before the deprecation notice. Slightly awkward phrasing ('in aesthetically pleasing color palette') but nothing wasteful.

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 simple zero-required-parameter generator with full schema coverage and no output schema, the description covers purpose and deprecation adequately. The main omission is that it never states the return value is a hex string, though 'css hex color code' strongly implies it.

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%, with each of redBase/greenBase/blueBase documented including the 0-255 range, so the schema already does the work. The description never mentions the base parameters or how they interact with the palette constraint, so it adds no meaning beyond the schema.

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 output resource: generates a random CSS hex color code, and adds the qualifier that the result comes from an aesthetically pleasing palette. That distinguishes it from raw random RGB generation, though it does not explicitly contrast with siblings like color-rgb or color-hsl.

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?

The deprecation note gives a clear when-not-to-use signal and names specific replacements (faker.color.rgb() or other color methods). It does not describe when this tool would still be the right choice, but the effective guidance is clear.

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