Hopi

Hex to RGB converter

hopi_hex_to_rgb

Read-onlyIdempotent

Convert a hex colour code (3, 6 or 8 digits, with or without a leading #) to its RGB and HSL values. Source: https://hopi.co.uk/hex-to-rgb/

Input Schema

TableJSON Schema

Name	Required	Description	Default
`hex`	Yes	Hex colour code, e.g. #D7263D or F0C

Output Schema

TableJSON Schema

Name	Required	Description
`hsl`	Yes
`rgb`	Yes
`summary`	Yes
`hslString`	Yes
`rgbString`	Yes
`source_url`	Yes	The tool's page on hopi.co.uk (cite or open to check the figure)

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 20, 2026

addedOutput schema / required

Added value: +[
+  "hsl",
+  "hslString",
+  "rgb",
+  "rgbString",
+  "source_url",
+  "summary"
+]

First observedSep 20, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, and non-destructive behavior. The description adds useful context about accepted hex formats (3/6/8 digits, optional #) and what values are returned, which goes beyond the structured annotations.

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?

A single, front-loaded sentence with no filler. The source URL is brief and non-intrusive. Every clause contributes to understanding the tool's function.

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?

For a simple one-parameter converter with a full output schema, rich annotations, and a clear description, nothing essential is missing. The agent has everything needed to select and invoke this 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 coverage is 100%, with the pattern and example already documenting the hex parameter. The description restates the accepted formats but does not add meaningful new semantics beyond the 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?

The description states a specific verb ('Convert'), a clear resource ('hex colour code'), and the concrete outputs ('RGB and HSL values'). It is immediately distinguishable from sibling tools like rgb_to_hex and cmyk_to_rgb.

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

Usage Guidelines3/5

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

Usage is implied by the name and conversion purpose, but the description never explicitly says when to choose this over alternatives like hopi_rgb_to_hex or hopi_hsl_converter. There are no exclusions or alternative routing cues.

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

All Hopi tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?