Skip to main content
Glama
colorjs

Color Space

Official
by colorjs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Space catalog

spaces
Read-onlyIdempotent

List and filter 221 color space definitions by family, purpose, or search terms to find the right one for display, video, camera, print, or research.

Instructions

List the 221 color spaces with display name, family, purpose, channels and one-line use. Optional filters: query (words matched against id, name, use line and description; best matches first), family, purpose.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNofree text, e.g. 'camera log', 'cielab', 'display p3'
familyNo
purposeNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countYes
spacesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv3.5.0
    • changedInput schema / properties / family / enum
      Previous value: -[
-  "Display & web",
-  "RGB remixes",
-  "Perceptual",
-  "Colorimetry & research",
-  "Video & broadcast",
-  "Film & camera",
-  "Print & paint"
-]New value: +[
+  "Display & web",
+  "Cylindrical",
+  "Perceptual",
+  "Colorimetry & research",
+  "Video",
+  "Camera",
+  "Print"
+]
    • changedInput schema / properties / purpose / enum
      Previous value: -[
-  "picking",
-  "palettes",
-  "editing",
-  "compositing",
-  "grading",
-  "delivery",
-  "print",
-  "difference",
-  "measurement",
-  "research"
-]New value: +[
+  "picking",
+  "palettes",
+  "editing",
+  "compositing",
+  "grading",
+  "delivery",
+  "print",
+  "difference",
+  "research"
+]
  2. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely useful behavior: the fixed size of the catalog (221), the exact fields returned, and that `query` results are relevance-ranked ('best matches first'), which the schema does not convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences: the first front-loads what the tool returns, the second covers filters. No filler, and the most decision-relevant information (scope and result shape) comes first.

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

Completeness4/5

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

For a simple read-only listing with an output schema and full safety annotations, this covers what an agent needs: scope, returned fields, and filter behavior. The only gap is the absence of routing guidance relative to the many siblings (`space`, `convert`, `gamut`) that could plausibly be confused with it.

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 coverage is only 33% (only `query` has a schema description), so the description must compensate. It does well for `query`, spelling out the fields matched against and the ordering, but `family` and `purpose` are merely named; their enum values carry the meaning and no filtering semantics (single vs multiple, combinability) are explained.

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 ('List the 221 color spaces') plus the fields returned, so the agent knows this is a catalog/browse operation. It does not explicitly contrast itself with the singular `space` sibling or `convert`, so sibling differentiation is only implicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Optional filters' implies that unfiltered listing is the default and filters narrow results, which is reasonable implied usage. However, no alternative tool is named and there is no when-to-use/when-not guidance (e.g. use `space` for a single space, `convert` for transformations).

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