Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

color-hwb

Generate an HWB color in CSS, binary, or decimal format to create realistic color data for testing and prototyping.

Instructions

Returns an HWB 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-hwb"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatNoFormat of generated HWB color.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.2

TDQS

C2.6/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 disclosure burden, and it discloses almost nothing: not whether the value is randomly generated, not the default format when 'format' is omitted, not the shape of the returned value, and not whether output is a string or object. For a generator tool with zero annotation coverage 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?

The single sentence is front-loaded and free of padding, with no redundancy. Its brevity is efficient, though it edges toward under-specification rather than tightness.

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?

The tool is simple (one optional enum parameter, no nesting), but there is no output schema, so the description should say what an 'HWB color' looks like when returned and what the default format is. Neither is stated, leaving the return contract undefined.

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 the single optional 'format' parameter has an enum-like anyOf (css, binary, decimal) already documented in the schema. The description adds no meaning beyond that, so the baseline 3 applies; it does not compensate by stating which format is the default.

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

Purpose3/5

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

The description gives a verb ('Returns') and a resource ('an HWB color'), so an agent can infer this produces an HWB color value rather than converting one. But it largely restates the tool name 'color-hwb' and offers no distinguishing detail versus the many sibling color tools (color-rgb, color-hsl, color-lab, etc.) beyond the color space itself.

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 color-hsl, color-rgb, or color-human, and no mention of prerequisites, defaults, or exclusions. The agent must infer usage entirely from the name and the single 'format' parameter.

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