Skip to main content
Glama

Agent Data Tools: Full list (every tool as its own definition)

Color contrast check (WCAG): check the contrast ratio of two colors against WCAG accessibility levels

color_contrast
Read-only

WCAG 2 contrast ratio between a text colour and a background colour, with pass/fail for AA and AAA at normal and large text sizes. Use to check that a design is readable. Example: fg=#767676, bg=#ffffff. Price $0.01/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

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": {
      "fg": "<fg>",
      "bg": "<bg>"
    },
    "name": "color_contrast"
  }
}

Input Schema

NameRequiredDescriptionDefault
bgYesBackground colour
fgYesText colour

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Beyond the annotations, it explains the billing model ($0.01/call via x402 USDC or card key, first 25 free, failed calls free) and clarifies that repeats are not free — which explains the non-obvious idempotentHint=false despite a pure computation. It also confirms nothing is changed. It does not detail output format/pagination, but no output schema exists and the pass/fail levels are described.

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?

The core capability and result shape come first, followed by usage and billing. The pricing sentence is long but each clause (price, key alternative, free tier, failed-call policy, repeat cost) carries actionable information.

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 two-parameter computation tool with no output schema, the description covers the return semantics (ratio plus AA/AAA pass/fail at two text sizes), auth/pricing, and side-effect profile. Nothing needed to call it correctly is missing.

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%, so the baseline is 3, but the example 'fg=#767676, bg=#ffffff' demonstrates the accepted hex-colour string format that the bare schema ("Text colour", "Background colour") does not specify.

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?

States a specific verb and resource: computes the WCAG 2 contrast ratio between a text colour and a background colour, returning pass/fail for AA and AAA at normal and large text sizes. This is clearly distinguishable from generic siblings like color or color_palette.

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?

"Use to check that a design is readable" gives a clear usage context, reinforced by a concrete fg/bg example. There are no explicit exclusions or named alternatives, but no sibling appears to overlap, so the guidance is adequate.

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.