Skip to main content
Glama
Jambozx

OnlineCyberTools MCP (280+ filterable tools)

conversion_color_code

Read-onlyIdempotent

Convert a single color string between HEX, RGB, HSL, and HSV formats, returning all four representations at once along with normalized channel values. Accepts hex, rgb, hsl, hsv, and CSS color names.

Instructions

Color Code Converter. Convert a single color string between HEX, RGB, HSL, and HSV, returning all four representations at once plus normalized channel values. Accepts hex (#RGB or #RRGGBB), rgb()/comma-triple, hsl(), hsv(), and 140+ CSS color names; the inputFormat argument names the expected source notation but a CSS color name is always tried as a fallback. Use webdev_hex_color instead when you want richer single-color analysis (CMYK, harmony palettes, WCAG contrast), 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 (60 requests/min anonymous). Returns the color formatted as HEX, short HEX, RGB, HSL, and HSV strings, a preview hex, and r/g/b, h/s/l, h/sv/v, and brightness values.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
inputYesThe color to convert. Format must match inputFormat: hex is #RGB/#RRGGBB, rgb is rgb(255,0,0) or a bare 255,0,0 triple, hsl is hsl(210,80%,60%) or 210,80,60, hsv is hsv(210,80%,60%) or 210,80,60. A CSS color name (red, teal, etc.) is accepted in any mode. Whitespace and case are ignored. Invalid input returns HTTP 400.
inputFormatNoThe expected source notation of input. Determines which parser runs first; a CSS color name is tried as a fallback regardless.hex

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
successNoWhether the conversion succeeded.
resultNoThe color expressed in every supported format.
Behavior5/5

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

Adds context beyond annotations: runs locally, no external service, rate limit of 60 req/min, and invalid input returns HTTP 400. No contradiction with annotations.

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?

Well-structured, front-loaded with purpose. Slightly verbose but clear and provides all necessary information in a single paragraph.

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 output schema exists, description covers input format, output, behavior, alternatives, and constraints fully. No gaps for an agent to use effectively.

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 is 100% but description adds parsing behavior (fallback to CSS color names), examples, and default behavior for inputFormat, enhancing understanding.

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 converts a single color string between HEX, RGB, HSL, and HSV, returning all four representations. Distinguishes from siblings webdev_hex_color and webdev_color_palette with specific use cases.

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 tells when to use alternatives: webdev_hex_color for richer analysis, webdev_color_palette for harmony schemes. Also mentions it's read-only, non-destructive, and rate-limited, guiding proper usage.

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