Skip to main content
Glama
Sign In

Burs-IA Utils

by io.github.soyeladice-svg
OverviewDiscussionsAdmin

Paleta de armonía de color

color-palette
Read-onlyIdempotent

Genera paletas armónicas desde un color base: complementaria, análoga, triádica, complementaria dividida, tetrádica o monocromática. Cuándo: hay que calcular con exactitud colores, contrastes o paletas, p. ej. para revisar accesibilidad. No para: convertir colores CSS (color-convert). 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: Generates harmony palettes from a base color by rotating OKLCH hue: complementary, analogous, triadic, split-complementary, tetradic (square) or monochromatic (lightness steps). When: color values, contrast or palettes have to be computed exactly, e.g. for accessibility checks. Not for: parsing any common CSS color (color-convert). 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

NameRequiredDescriptionDefault
colorYesBase color (string; required; up to 100 chars).
countNoColors for monochromatic (integer; optional; default 5; min 2; max 12).
schemeYesHarmony (required; one of: complementary, analogous, triadic, split_complementary, tetradic, monochromatic).

Output Schema

NameRequiredDescriptionDefault
colorsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / color / examples
      Added value: +[
+  "#3366cc"
+]
    • addedInput schema / properties / scheme / examples
      Added value: +[
+  "complementary"
+]
  2. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the 'readOnlyHint' in annotations, the description provides rich behavioral context, including 'no network access,' 'deterministic' behavior, and specific operational limits (time/size constraints). This significantly enhances the agent's understanding of the tool's operational constraints.

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?

The description is exceptionally well-structured, using clear headings (When, Not for, Effects, Limits) to front-load and categorize high-value information efficiently.

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?

The definition is complete for a multi-schema, complex function. It covers all necessary usage conditions, constraints, and safety profiles, leaving no major gap for the agent to fill.

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?

Although the schema coverage is 100%, the description adds crucial semantic value by explaining the conceptual roles of the inputs—namely, that the calculation is intended for precise tasks like accessibility checks.

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?

The description clearly defines the function as generating harmonic color palettes using specific methods (complementary, analogous, etc.) and immediately differentiates itself from sibling tools like color-convert.

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?

It provides explicit usage guidelines ('When:') and specific exclusions ('Not for: converting colors CSS (color-convert)'), preventing misuse and routing the agent correctly to alternative tools.

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 toolsInspect
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