Burs-IA Utils

Diferencia de color (ΔE 2000)

color-delta-e

Read-onlyIdempotent

Calcula la diferencia perceptual entre dos colores: ΔE CIEDE2000 y ΔE OKLab, con interpretación. Cuándo: hay que calcular con exactitud colores, contrastes o paletas, p. ej. para revisar accesibilidad. No para: calcular la relación de contraste WCAG entre dos colores (color-contrast). 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: Computes the perceptual difference between two colors: CIEDE2000 ΔE (CIELAB D65) and Euclidean OKLab ΔE, with a plain-language interpretation (< 1 imperceptible … > 10 very different). When: color values, contrast or palettes have to be computed exactly, e.g. for accessibility checks. Not for: computing the WCAG contrast ratio of two colors (color-contrast). Side effects: none (read-only, no network access, no stored state). [EN completo / full EN: inputSchema.description]

Input Schema

Name	Required	Description	Default
`a`	Yes	First color (string; required; up to 100 chars).
`b`	Yes	Second color (string; required; up to 100 chars).

Output Schema

Name	Required	Description	Default
`delta_e_2000`	No
`delta_e_oklab`	No
`interpretation`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 2, 2026
- addedInput schema / properties / a / examples
```
Added value: +[
+  "#ff0000"
+]
```
- addedInput schema / properties / b / examples
```
Added value: +[
+  "#fe0000"
+]
```

Changed1 schema field changedNov 1, 2026

addedInput schema / description

Added value: +"EN: Computes the perceptual difference between two colors: CIEDE2000 ΔE (CIELAB D65) and Euclidean OKLab ΔE, with a plain-language interpretation (< 1 imperceptible … > 10 very different). When: color values, contrast or palettes have to be computed exactly, e.g. for accessibility checks. Not for: computing the WCAG contrast ratio of two colors (color-contrast). 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."

First observedNov 1, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnly, closed-world, idempotent and non-destructive, and the description reinforces these (no network, no stored state, deterministic) rather than contradicting them. It then adds information the annotations cannot carry: hard limits (64 KB input, 1 s per call, 1 MB result) and the interpretation thresholds (<1 imperceptible … >10 very different), which materially affects how an agent reads the result.

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?

Each language block is tightly front-loaded: purpose, when, not-for, side effects, limits. The full text is roughly doubled by the ES/EN bilingual pairing and the redundant 'deterministic' sentence, which costs some density but serves the declared locale context.

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?

Output schema exists, so return-shape explanation is not required, yet the description still gives the interpretation scale an agent needs to narrate results. With limits, side effects, determinism and sibling disambiguation all present, nothing needed to call this correctly is missing.

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 two required params 'a' and 'b' are already documented with examples and max lengths — baseline 3. The description adds nothing about accepted color formats (hex only? rgb()? named colors?), which is the one parameter question the schema leaves unanswered.

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?

Names the exact operation and both metrics ('CIEDE2000 ΔE (CIELAB D65)' and 'Euclidean OKLab ΔE') plus the plain-language interpretation band. It also distinguishes itself from the nearest sibling by name (color-contrast), so an agent can route correctly without opening either 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?

Explicit 'When' clause (exact color/contrast/palette computation, e.g. accessibility checks) and an explicit 'Not for' clause naming the WCAG contrast-ratio tool. Both the positive and negative selection conditions are given.

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?