Color Brightness Analysis for AI AgentsColor Brightness Analysis for AI Agents

OnlineCredit Usage:1 per callTool:ColorBrightnessAnalysisforAIAgents

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 VerveContext MCP server, this appears in its tool list as ColorBrightnessAnalysisforAIAgents. 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.

Tool call
{
  "name": "ColorBrightnessAnalysisforAIAgents",
  "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 ColorBrightnessAnalysisforAIAgents on its own.

Connecting

One server URL covers every source 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.

Client config
{
  "mcpServers": {
    "vervecontext": {
      "url": "https://api.vervecontext.com/v1/mcp"
    }
  }
}
Endpoint
https://api.vervecontext.com/v1/mcp

Per-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.

ArgumentTypeExampleDescription
hexRequiredstringFF5733Hex 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.

Result
{
  "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

Fields marked Premium need a paid plan. On a plan without them the key is absent rather than wrong, so a model never reasons over a substituted value.
FieldTypeExampleDescription
hexstring#FF5733Hexadecimal color value provided in the request
rgbobject{…}RGB color components: red, green, blue values
rgb.rnumber255Red component value between 0 and 255
rgb.gnumber87Green component value between 0 and 255
rgb.bnumber51Blue component value between 0 and 255
luminancePremiumnumber0.2832Relative luminance calculated using WCAG 2.0 formula
perceived_brightnessPremiumnumber131Perceived brightness score from 0 to 255
yiqPremiumnumber133.13YIQ color space brightness value for brightness analysis
is_lightbooleanfalseBoolean indicating if color is considered light
is_darkbooleantrueBoolean indicating if color is considered dark
brightness_categorystringdarkBrightness classification: light, medium, or dark category
recommended_text_colorPremiumstring#FFFFFFRecommended text color for optimal contrast and readability
contrast_ratio_with_whitePremiumnumber3.15WCAG contrast ratio calculation between color and white
contrast_ratio_with_blackPremiumnumber6.66WCAG contrast ratio calculation between color and black
wcag_aa_compliant_with_whitePremiumbooleanfalseWhether color meets WCAG AA contrast requirements with white
wcag_aa_compliant_with_blackPremiumbooleantrueWhether color meets WCAG AA contrast requirements with black
wcag_aaa_compliant_with_whitePremiumbooleanfalseWhether color meets WCAG AAA contrast requirements with white
wcag_aaa_compliant_with_blackPremiumbooleanfalseWhether color meets WCAG AAA contrast requirements with black

Why ground on it

A model can produce something that looks like this answer from its training data, and be confidently out of date or simply wrong. This source returns the current value with a shape you can check, which is the difference between an answer you can cite and one you have to hedge.

Point an evaluation at is_light: it is the field most worth pinning a claim to, and it is either present and current or absent — never plausibly invented.

Failure modes

Errors come back as tool errors with a sentence the model can act on, not a bare status code.

StatusWhat it means
400 / 422The arguments didn't validate. The message names the offending one.
401The OAuth session is invalid or expired — reconnect the server.
403Out of credits. Not a bad key — the month's allowance is spent.
404This source isn't part of VerveContext. Check the catalog.
429Brief rate limit. Retrying after a moment succeeds.

Other ways to use Color Brightness Analysis for AI Agents

Set up Color Brightness Analysis for AI Agents on VerveContext, or reach the same source a different way. Your VerveContext account and credits work on all of them — one key, one balance.

Call it as a REST APIOne HTTPS endpoint and an X-API-Key header, with SDKs for Node, Python and .NET.APIVerveReference →
Give it to an AI agentConnect over MCP and your agent calls it as a native tool — Claude, Cursor, ChatGPT.VerveKitReference →
Use it in Google Sheets or ExcelA =VERVE() formula fills a column — no script, no export, recalculates in place.VerveSheetsReference →

Frequently asked questions

Do I have to tell the agent to use ColorBrightnessAnalysisforAIAgents?

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 VerveContext 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.

What's Next?

Continue your journey with these recommended resources

Was this page helpful?