Skip to main content
Glama

Launch page color contrast checker

toolfound_color_contrast
Read-onlyIdempotent

Calculate the WCAG text contrast ratio for two opaque hex colors before shipping a landing page or launch graphic. Returns an evidence-bounded result and the canonical web tool URL.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "foreground": "<foreground>",
      "background": "<background>"
    },
    "name": "toolfound_color_contrast"
  }
}

Input Schema

NameRequiredDescriptionDefault
backgroundYesBackground colour the text sits on, as an opaque hex code with a leading hash, for example #ffffff.
foregroundYesText colour as an opaque hex code with a leading hash, for example #1a2b3c or #fff.

Output Schema

NameRequiredDescriptionDefault
okYes
dataNo
linksYes
errorsNo
summaryYes
sectionsYes
canonical_result_urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / background / description
      Added value: +"Background colour the text sits on, as an opaque hex code with a leading hash, for example #ffffff."
    • addedInput schema / properties / foreground / description
      Added value: +"Text colour as an opaque hex code with a leading hash, for example #1a2b3c or #fff."
  2. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds two real behavioral facts beyond that: only opaque hex inputs are supported, and the result is 'evidence-bounded' with a canonical web tool URL. However, 'evidence-bounded result' is undefined jargon that gives the agent no concrete sense of the output shape.

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?

Two sentences, front-loaded with the calculation purpose and followed by the return characteristics, with no filler. The phrase 'evidence-bounded result' is the only wording that does not clearly earn its place because it is not self-explanatory.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter, read-only, idempotent calculation tool with a full output schema and complete annotation coverage, the description supplies purpose, input constraint, and a hint about the return payload. Nothing essential is missing, though the vague 'evidence-bounded' phrase leaves the result nature slightly underspecified relative to what the output schema presumably shows.

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 description coverage is 100%, so both parameters (foreground and background) are already documented with hex format and examples. The description's phrase 'two opaque hex colors' reinforces the alpha-channel restriction but mostly restates what the schema already states, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource: 'Calculate the WCAG text contrast ratio for two opaque hex colors.' No sibling tool in the list performs color or contrast work, so differentiation is implicit rather than stated, which is why this lands at 4 rather than 5.

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

Usage Guidelines4/5

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

'before shipping a landing page or launch graphic' gives an explicit use context tied to a launch workflow, which is clear guidance for when to reach for it. It stops short of naming when-not-to-use conditions or alternatives (e.g. checking non-text contrast or alpha colors elsewhere).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources