Burs-IA Utils

Aclarar, oscurecer o saturar color

color-adjust

Read-onlyIdempotent

Ajusta un color en OKLCH: luminosidad, croma (saturación) y tono, o transparencia. Cuándo: hay que calcular con exactitud colores, contrastes o paletas, p. ej. para revisar accesibilidad. No para: encontrar el color más cercano (color-contrast-fix). Efectos secundarios: ninguno (solo lectura, sin red, sin estado guardado). Determinista: la misma entrada da la misma salida. Límites: entrada JSON de hasta 64 KB, 1 s por llamada, resultado de hasta 1 MB.

EN: Adjusts a color in OKLCH: change lightness, chroma (saturation) and hue by deltas, or set alpha; results are mapped back into the sRGB gamut. When: color values, contrast or palettes have to be computed exactly, e.g. for accessibility checks. Not for: finding the closest color to a foreground (color-contrast-fix). Side effects: none (read-only, no network access, no stored state). Deterministic: the same input gives the same output. Limits: JSON input up to 64 KB, 1 s per call, result up to 1 MB.

Input Schema

Name	Required	Description
`hue`	No	Hue rotation in degrees (number; optional; default 0; min -360; max 360).
`alpha`	No	Set alpha 0-1 (number; optional; min 0; max 1).
`color`	Yes	CSS color: hex, rgb(), hsl(), hwb(), oklch(), oklab() or a named color (string; required; up to 100 chars).
`chroma`	No	Chroma delta (-0.4..0.4) (number; optional; default 0; min -0.4; max 0.4).
`lightness`	No	Lightness delta (-1..1) (number; optional; default 0; min -1; max 1).

Output Schema

Name	Required	Description	Default
`color`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 2, 2026
- addedInput schema / properties / color / examples
```
Added value: +[
+  "#3366cc"
+]
```
First observedNov 1, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Adds real context beyond the annotations: no network access, no stored state, deterministic behavior, and hard limits (64 KB input, 1 s per call, 1 MB result), plus the sRGB gamut-mapping behavior. The 'read-only' clause duplicates readOnlyHint=true, so it is not entirely additive, but the limits and determinism disclosure are valuable for a compute tool.

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?

Front-loaded with the operation, then cleanly labeled blocks (When / Not for / Side effects / Deterministic / Limits). The full Spanish and English text is duplicated, which is redundant for a reader but appears intentional for this server; within each language every sentence earns its place.

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

Completeness5/5

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

An output schema exists, so return values need no explanation. The description still covers the operation, the gamut-mapping result, usage routing, side-effect profile, determinism, and operational limits — everything needed to invoke a 5-parameter pure-compute tool correctly.

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 baseline is 3. The description's 'lightness, chroma (saturation) and hue by deltas, or set alpha' mirrors what each property already documents (delta ranges, optionality, defaults), adding only the gloss that chroma means saturation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Adjusts a color in OKLCH') plus the exact axes being modified (lightness, chroma, hue deltas, alpha) and the gamut-mapping outcome. It explicitly names the sibling it is not (color-contrast-fix), so an agent can distinguish it without opening the schema.

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

Usage Guidelines5/5

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

Has explicit 'When:' (exact color/contrast/palette computation, e.g. accessibility checks) and 'Not for:' (finding the closest color, routed to color-contrast-fix). Both the positive trigger and the exclusion are stated, leaving nothing to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Burs-IA Utils tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?