Skip to main content
Glama

Choose black or white foreground

bpj_choose_monochrome_foreground
Read-onlyIdempotent

Rank black and white foregrounds by their WCAG contrast against the supplied background.

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": {
      "color": "<color>"
    },
    "name": "bpj_choose_monochrome_foreground"
  }
}

Input Schema

NameRequiredDescriptionDefault
colorYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, closed-world, non-destructive behavior, so the safety profile is covered. The description adds the useful behavioral detail that ranking is by WCAG contrast against the background, but it does not say what the return looks like — a single chosen color versus an ordered pair — which is the key behavioral question for a 'rank' tool with no output schema.

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?

A single front-loaded sentence with no filler; the contrast criterion appears immediately. It is arguably too terse for a tool whose return shape is unclear, but nothing in it is wasted or redundant.

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

Completeness3/5

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

With one simple parameter and no output schema, the definition conveys the core operation adequately but leaves the return value (ranked list vs single selection) and the expected hex input format unspecified. For a low-complexity tool these gaps are small but real, since the name promises 'choose' while the description promises 'rank'.

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 0%, so the description must compensate; it does add real meaning by identifying the single 'color' parameter as the background against which foregrounds are judged. It does not add any format detail (leading '#', 6-digit requirement, maxLength 7) beyond the schema's title, leaving the coverage gap only partially filled.

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 operation and resource: ranking black and white foregrounds, with the criterion stated as WCAG contrast against the supplied background. An agent can tell this is a contrast-based text-color selector, though it never reconciles the 'rank' wording with the 'choose' wording in the name/title (i.e., whether one color or both ranked are returned).

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 only implied: given a background color, evaluate black vs white as foreground. There is no explicit when-to-use statement, no preconditions, and no mention of when this is inappropriate (e.g., non-opaque backgrounds or when a non-monochrome foreground is wanted), and siblings are unrelated enough that no exclusion is offered.

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.