Skip to main content
Glama

AutoTasker Hub — China Social Data API

color_info

Color info (name, RGB, HSL, HSV, CMYK) for any hex code. Design helper. $0.01 USDC.

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": {
      "hex": "<hex>"
    },
    "name": "color_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
hexYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden; it does identify the return values (name, RGB, HSL, HSV, CMYK) and the $0.01 USDC cost, which is genuinely useful. It says nothing about whether input validation failures are handled, external lookups, or rate limits, and never explicitly states the operation is a read-only computation.

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?

Three short fragments, front-loaded with the core purpose and output list. The "$0.01 USDC" cost note takes space that could have gone to the hex format detail, but it is not padding.

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 one-parameter lookup with no output schema, the description adequately states inputs and outputs. The gaps are the hex input format and any statement of what happens with invalid input, which matter for reliable invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/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 for the single hex parameter, and it only says "any hex code." It does not clarify accepted formats (leading #, 3-digit shorthand, case sensitivity), which is the one detail that would most affect a successful call.

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?

"Color info (name, RGB, HSL, HSV, CMYK) for any hex code" names the resource and enumerates the exact conversions returned, so an agent knows precisely what it gets. It does not differentiate itself from the sibling color_scheme, leaving that distinction to inference.

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

Usage Guidelines2/5

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

The only usage hint is the terse tag "Design helper," which gestures at a context but names no alternatives and no when-not-to-use conditions. An agent must decide on its own whether color_scheme would be the better call.

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.