GadgetHumans API Hub

color_palette

Generate a harmonious palette (complementary, analogous, triadic) from a seed colour, with hex values. Pure CPU, instant.

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": "color_palette"
  }
}

Input Schema

Name	Required	Description	Default
`color`	Yes	Seed colour
`scheme`	No	complementary, analogous or triadic

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 8, 2026
RemovedNov 6, 2026

Changed3 schema fields changedNov 3, 2026

addedInput schema / properties / color

Added value: +{
+  "description": "Seed colour",
+  "type": "string"
+}

addedInput schema / properties / scheme

Added value: +{
+  "description": "complementary, analogous or triadic",
+  "type": "string"
+}

addedInput schema / required
```
Added value: +[
+  "color"
+]
```

AddedNov 2, 2026

TDQS

B3.4/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It usefully discloses that the operation is pure CPU and instant and that results are hex values, but says nothing about what happens when scheme is omitted (no default given) or about the shape/size of the returned palette.

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 short, front-loaded sentences with no filler; the latency note is compact and informative. Slightly thin rather than bloated, but nothing is wasted.

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?

For a simple two-parameter tool with an optional scheme, the definition covers the core purpose and output format, but leaves the optional-parameter default and result structure unexplained with no output schema to fall back on.

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 the baseline is 3. The description merely restates the scheme values already in the schema and adds no meaning such as a default scheme or accepted colour input formats (named colours vs hex).

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?

States a specific verb and resource ("Generate a harmonious palette") and names the concrete scheme types plus the output format (hex). It does not distinguish itself from near-identical siblings such as color_harmony or color_contrast, so an agent cannot tell from the description alone which of those to call.

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 by the phrase "from a seed colour" and the scheme list; there is no explicit when-to-use or when-not-to-use guidance and no routing to alternatives like color_harmony or color_contrast.

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

All GadgetHumans API Hub tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.