DS4AI MCP

solve_palette

Solve a full TEMPER palette to verify contrast floors for a specified mode, notch, family, and vision constraint, returning the semantic token set.

Instructions

Solve a full TEMPER palette to verified contrast floors for a mode. mode is light, soft-light, soft-dark, or dark; notch is 0 (brighter), 1 (middle), or 2 (deeper); family is a color family key (for example iron, oxblood, moss); vision constrains for a color-vision deficiency (default, rg, by, mono). Returns the semantic token set.

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": {
      "mode": "<mode>"
    },
    "name": "solve_palette"
  }
}

Input Schema

Name	Required	Description	Default
`mode`	Yes
`notch`	No
`family`	No
`vision`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 21, 2026

TDQS

A4/5.0

Behavior3/5

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

The description states it returns the semantic token set, but provides no information about side effects, errors, or permissions. With no annotations, more behavioral detail would be beneficial.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that packs all necessary parameter explanations and the return type without redundancy.

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?

The description adequately covers parameters and return, but lacks deeper context on what 'verified contrast floors' entails or any constraints, though it's reasonably complete for a domain-specific tool.

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?

The description clarifies each parameter (mode, notch, family, vision) with enums and examples, adding meaning beyond the schema's bare types and enums, though not exhaustive.

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?

The description clearly states the tool solves a TEMPER palette to verified contrast floors, which is specific and distinct from sibling tools like audit_surface or generate_head.

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?

The description does not explicitly mention when to use this tool over alternatives, nor does it provide usage context beyond the operation itself.

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

Deploy Server