Color Brightness Skill
The tool
Color Brightness Calculator provides comprehensive brightness analysis including relative luminance, perceived brightness, YIQ calculations, and WCAG AA/AAA contrast compliance with recommended text colors.
Once your client is connected to the VerveKit MCP server, this appears in its tool list as ColorBrightnessSkill. It is read-only and open-world: it fetches, it never mutates anything on your side, so most clients will call it without asking you to confirm.
{
"name": "ColorBrightnessSkill",
"arguments": {
"hex": "FF5733"
}
}What that looks like in a conversation
You don't name the tool — the model picks it. Asking about FF5733 in the terms this source covers is enough for it to reach for ColorBrightnessSkill on its own.
Connecting
One server URL covers every skill in the catalog, including this one. Authorization is OAuth — the client opens a browser once and there is no key to paste into a config file.
{
"mcpServers": {
"vervekit": {
"url": "https://api.vervekit.com/v1/mcp"
}
}
}https://api.vervekit.com/v1/mcpPer-client setup — Claude Desktop, Cursor, VS Code, ChatGPT — is on the MCP setup page.
Arguments
These are the properties on the tool's inputSchema, so a well-behaved client validates them before the call is made.
| Argument | Type | Example | Description |
|---|---|---|---|
hexRequired | string | FF5733 | Hex color value (with or without # prefix) |
What the model gets back
The result carries a structuredContent object matching the tool's declared outputSchema, so a client can read fields without parsing prose. status is "ok" on success and error is null; a null field means the value wasn't available for that input, not that the call failed.
{
"status": "ok",
"error": null,
"data": {
"hex": "#FF5733",
"rgb": {
"r": 255,
"g": 87,
"b": 51
},
"luminance": 0.2832,
"perceived_brightness": 131,
"yiq": 133.13,
"is_light": false,
"is_dark": true,
"brightness_category": "dark",
"recommended_text_color": "#FFFFFF",
"contrast_ratio_with_white": 3.15,
"contrast_ratio_with_black": 6.66,
"wcag_aa_compliant_with_white": false,
"wcag_aa_compliant_with_black": true,
"wcag_aaa_compliant_with_white": false,
"wcag_aaa_compliant_with_black": false
}
}Fields
| Field | Type | Example | Description |
|---|---|---|---|
hex | string | #FF5733 | Hexadecimal color value provided in the request |
rgb | object | {…} | RGB color components: red, green, blue values |
rgb.r | number | 255 | Red component value between 0 and 255 |
rgb.g | number | 87 | Green component value between 0 and 255 |
rgb.b | number | 51 | Blue component value between 0 and 255 |
luminancePremium | number | 0.2832 | Relative luminance calculated using WCAG 2.0 formula |
perceived_brightnessPremium | number | 131 | Perceived brightness score from 0 to 255 |
yiqPremium | number | 133.13 | YIQ color space brightness value for brightness analysis |
is_light | boolean | false | Boolean indicating if color is considered light |
is_dark | boolean | true | Boolean indicating if color is considered dark |
brightness_category | string | dark | Brightness classification: light, medium, or dark category |
recommended_text_colorPremium | string | #FFFFFF | Recommended text color for optimal contrast and readability |
contrast_ratio_with_whitePremium | number | 3.15 | WCAG contrast ratio calculation between color and white |
contrast_ratio_with_blackPremium | number | 6.66 | WCAG contrast ratio calculation between color and black |
wcag_aa_compliant_with_whitePremium | boolean | false | Whether color meets WCAG AA contrast requirements with white |
wcag_aa_compliant_with_blackPremium | boolean | true | Whether color meets WCAG AA contrast requirements with black |
wcag_aaa_compliant_with_whitePremium | boolean | false | Whether color meets WCAG AAA contrast requirements with white |
wcag_aaa_compliant_with_blackPremium | boolean | false | Whether color meets WCAG AAA contrast requirements with black |
Failure modes
Errors come back as tool errors with a sentence the model can act on, not a bare status code.
| Status | What it means |
|---|---|
400 / 422 | The arguments didn't validate. The message names the offending one. |
401 | The OAuth session is invalid or expired — reconnect the server. |
403 | Out of credits. Not a bad key — the month's allowance is spent. |
404 | This skill isn't part of VerveKit. Check the catalog. |
429 | Brief rate limit. Retrying after a moment succeeds. |
Other ways to use Color Brightness Skill
Set up Color Brightness Skill on VerveKit, or reach the same source a different way. Your VerveKit account and credits work on all of them — one key, one balance.
Frequently asked questions
Do I have to tell the agent to use ColorBrightnessSkill?
No. The tool's name and description are in the model's context once the server is connected, so it selects the tool when the question calls for it. Naming it explicitly works too and is useful when you want to force the call.
Does connecting the server expose every tool at once?
Yes — one connection lists the whole VerveKit catalog. Clients with a tool budget can usually filter the list; the credit cost is per call, so an unused tool costs nothing.
What does a call cost?
1 credit each time the tool actually runs. A model that reasons about the tool without calling it costs nothing.
Is there a REST version of this?
Yes — the same source is available as a plain HTTPS endpoint on APIVerve, linked above. Same data, same credits, same account.