Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

color-cssSupportedSpace

Returns a random CSS-supported color space name for generating mock data or testing color-related features.

Instructions

Returns a random css supported color space name.

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-cssSupportedSpace"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.2

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the key non-obvious trait: the result is random, so repeated calls may differ. However, it says nothing about what the returned value actually looks like (a bare string name such as 'srgb' vs. an object) or whether the selection is uniform, leaving meaningful behavioral gaps.

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 short sentence with no filler, and the key trait (random) is present from the start. Minor deduction for the slightly garbled 'css supported' phrasing, which costs a little clarity.

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 zero-parameter utility there is no output schema and no annotations, so the description is the only source of truth about results. It covers randomness but omits the return type and example values, which is the main thing an agent would still need to know.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is nothing for the description to elaborate on; the 100% schema coverage confirms an empty object schema. A baseline of 4 applies.

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?

The description states a specific verb (Returns) and a specific resource (a random CSS-supported color space name), which is enough to distinguish it from most siblings conceptually. The phrase 'css supported color space name' is somewhat awkward but still concrete about what is produced.

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 call this versus alternatives such as color-space or color-cssSupportedFunction, and no stated use case (e.g., generating test data or picking a random space for examples). The agent must infer intent 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