Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

color-lab

Generate CIELAB (LAB) color values in CSS, binary, or decimal formats for fake data generation and testing.

Instructions

Returns a LAB (CIELAB) 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-lab"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatNoFormat of generated LAB color.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.2

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description bears the full behavioral burden but says almost nothing. It does not disclose whether the color is randomly generated or deterministic, whether the result is reproducible, or what the css/binary/decimal formats mean in practice.

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?

A single compact sentence, front-loaded with the resource and output space, with no wasted words. Its brevity is a virtue structurally, though it borders on under-specification.

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

Completeness3/5

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

For a one-optional-parameter tool with no output schema and no annotations, this is thin but not reckless — the return type is stated in the name of the tool. It would be more complete if it clarified generation vs conversion and described the return value's shape.

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 single optional 'format' parameter with its css/binary/decimal options is already documented in structured data. The description adds nothing beyond that, which is the baseline expectation when the schema does the work.

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 resource: 'Returns a LAB (CIELAB) color.' This distinguishes it from sibling color tools like color-rgb and color-hsl by output space. However, it is ambiguous whether this generates a new color or converts an input color to LAB — the schema's 'generated LAB color' phrasing hints at generation but the description never resolves it.

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, and no stated prerequisites or exclusions. The agent must infer that it is the LAB-specific variant purely 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