Color Space
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| convertA | Convert a color between any two of the 221 color spaces, identity included, in each space's conventional ranges (rgb 0-255, oklch L 0-1 / C 0-0.4 / H 0-360, lab L 0-100 …). The color goes in as a CSS string ( |
| gamutA | Which standard display gamuts hold a color — sRGB ⊂ Display P3 ⊂ Rec. 2020, each tested in its own RGB box straight from the source space, the same ladder as the color-space.io gamut pill. |
| cssA | A color as CSS Color 4 strings — rgb(), hsl(), hwb(), lab(), lch(), oklab(), oklch() and color(display-p3 | a98-rgb | prophoto-rgb | rec2020 | srgb-linear | xyz-d65 | xyz-d50) — plus #hex inside sRGB. Converted, never gamut-mapped: a string is null where CSS would clamp it into a different color (rgb/hsl/hwb outside sRGB, lightness out of range). |
| spaceB | The dossier of one color space: display name (as color-space.io shows it), description, channels + conventional ranges, defining references, provenance (year, author), illuminant/observer, encoding class, family and purpose, and its direct conversion neighbours. |
| spacesA | List the 221 color spaces with display name, family, purpose, channels and one-line use. Optional filters: |
| cubeA | Render a conversion as a .cube LUT file (Resolve, Premiere, Final Cut, OBS, ffmpeg). The header carries the measured deviation vs the direct conversion. Pure per-channel transfers auto-emit 1D. Size ≤ 33 here (larger via the library or https://color-space.io/). |
| shaderA | The conversion as shader source – GLSL (WebGL2; WebGL1 too unless the path reads a table), WGSL (WebGPU), HLSL (DirectX, Unity, Unreal) or MSL (Metal) – with an entry function |
| iccA | One space as an ICC v2 profile (.icc): matrix + tone curve where the space is an RGB working space (Photoshop, OS color management), a CLUT on a Lab PCS otherwise (lcms, ArgyllCMS, ImageMagick). Returned as a base64 embedded resource; |
| codeA | The conversion as code to paste: the color-space JS call with its result and – where one exists for the space on the non-sRGB side – the colour-science (Python) equivalent verified against color-space (sRGB ↔ that space), with any named caveat. The color goes in as a CSS string or as values in |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| data.json | Every space: channels and ranges, references, provenance, gamuts, cited conformance points – the language-neutral artifact. |
TDQS
Scored across 9 tools
Each tool has a distinct primary output: raw conversion (convert), CSS strings (css), LUT file (cube), shader source (shader), ICC profile (icc), pasteable code (code), gamut membership (gamut), and space metadata (space/spaces). The only mild overlap is that convert, css, code, cube, shader, and icc all produce a conversion of a color, but the target format clearly separates them. Descriptions make the boundaries clear.
All names are single lowercase tokens with no mixed casing or hyphenation, which is predictable and readable. It is not a strict verb_noun pattern (convert is a verb; the rest are nouns like space, cube, shader), and space/spaces differ only by pluralization, but overall style is consistent.
Nine tools is well within a healthy range and each earns its place, covering distinct output formats and metadata queries without redundancy. The surface is neither thin nor bloated for a color-space library.
The surface covers conversion, gamut testing, CSS/LUT/shader/ICC/code emission, and full space metadata, which is strong lifecycle coverage for a color-space domain. Minor gaps exist (e.g. no color-difference/delta-E, interpolation, or blending operations), but core workflows are fully supported.