Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

color-cmyk

Generates CMYK color values in CSS, binary, or decimal format for design, testing, and color data generation.

Instructions

Returns a CMYK 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-cmyk"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatNoFormat of generated CMYK 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 burden. It does not disclose whether output is random or deterministic, what the return value's structure is, or what units/channel ranges apply — all critical for a color-generation tool.

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?

It is a single short sentence with no filler, but it is terse to the point of under-specification rather than appropriately sized. Nothing is front-loaded beyond the bare return type.

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?

Complexity is low (one optional param), but with no annotations and no output schema, the description is the only place to explain the returned CMYK value's shape and semantics, and it omits that entirely.

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 with its css/binary/decimal enum alternatives is fully documented in the schema. The description adds nothing about when to prefer a given format, so the baseline 3 applies.

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 a CMYK color" essentially restates the name color-cmyk with a verb attached. It does not clarify whether the tool generates a random/arbitrary CMYK color, converts something, or returns a fixed default — and with no color input parameter, that ambiguity is the main thing an agent needs resolved.

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 choose this over sibling color tools such as color-rgb, color-hsl, color-lab, or color-hwb, and no stated preconditions. The agent must infer usage from the 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