Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

color-hsl

Generate an HSL color value, optionally with alpha, in CSS, decimal, or binary format for fake data and UI testing.

Instructions

Returns an HSL 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-hsl"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatNoFormat of generated HSL color.
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 provided, so the description carries the full disclosure burden and fails it: nothing says whether each call produces a new random color or a stable value, whether values are valid CSS, or how the binary format behaves. Reading "Returns" suggests a non-destructive read, which is the only behavioral signal present.

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 front-loaded and free of padding, so there is no waste, but the brevity reflects under-specification rather than economy. The space saved is space that should have carried behavior and usage detail.

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?

There is no output schema, so the description must explain what is actually returned — a CSS HSL string versus a binary payload — and it does not, even though the format parameter makes that distinction real. For a generator tool with zero annotations, this leaves the agent guessing at the core output.

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 only two optional parameters (format, includeAlpha), and both carry inline descriptions, so the baseline is 3. The description adds nothing about defaults or valid combinations, but the schema already does the explanatory work.

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 HSL color" restates the tool name almost verbatim; the only added information is the acronym expansion. It gives no hint of whether the color is random, generated from a seed, or derived from input, and it does not distinguish this from sibling generators like color-rgb or color-hwb.

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 when-to-use guidance, no mention of when to prefer HSL over the sibling RGB/HWB/CMYK/LAB color tools, and no statement of preconditions. The agent must infer the choice from the tool name alone.

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