Skip to main content
Glama
Jambozx

OnlineCyberTools MCP (280+ filterable tools)

webdev_hex_color

Read-onlyIdempotent

Parse any color string and get HEX, RGB, HSL, HSV, CMYK values, plus four color palettes and WCAG accessibility analysis. Supports hex, rgb(), hsl(), and CSS color names.

Instructions

Hex Color Viewer And Analyzer. Parse a single color string and return it in every format (HEX, RGB, HSL, HSV, CMYK) plus four generated palettes and a WCAG accessibility analysis. Accepts hex (#RGB, #RRGGBB, 0x-prefixed), rgb()/rgba(), a bare r,g,b triple, hsl(), and 21 CSS color names — it auto-detects the format, so no source-format argument is needed. Use conversion_color_code for a focused HEX/RGB/HSL/HSV conversion between two chosen formats, or webdev_color_palette when you only want harmony schemes. Runs locally on the input you provide: read-only, non-destructive, contacts no external service, and is rate-limited. Returns the all-format color, monochromatic/analogous/complementary/triadic palettes, and brightness, contrast, temperature, and suggested-text-color analysis.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
inputYesThe color to parse, in any supported notation: a hex value (#RGB, #RRGGBB, or 0xRRGGBB), rgb()/rgba(), a bare r,g,b triple, hsl(), or a CSS color name (red, blue, teal, etc.). Whitespace and case are ignored. Invalid input returns HTTP 400.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
successNoWhether parsing succeeded.
inputNoThe input color string, echoed back.
colorNoThe color expressed in all supported formats.
palettesNoGenerated harmony palettes, each an array of #RRGGBB hex strings.
analysisNoPerceptual and WCAG accessibility analysis of the color.
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. Description adds valuable operational context: runs locally, no external service, rate-limited. No contradictions.

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 sentences that efficiently convey purpose, capabilities, usage guidelines, and behavioral traits. Front-loaded with main action. 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?

Given tool complexity (multiple formats, palettes, analysis), description covers all key aspects. Output schema exists, but description still details return content. No gaps.

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?

Schema coverage 100% with detailed description and examples. Description adds that whitespace and case are ignored, and invalid input returns HTTP 400, enhancing understanding beyond schema.

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?

Clearly states it parses a color string and returns multiple formats, palettes, and WCAG analysis. Explicitly distinguishes from sibling tools conversion_color_code and webdev_color_palette.

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?

Explicitly advises when to use alternatives: 'Use conversion_color_code for a focused HEX/RGB/HSL/HSV conversion... or webdev_color_palette when you only want harmony schemes.'

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Jambozx/onlinecybertools-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server