ZapifyAPI MCP Server

convert_color

Convert color values between HEX, RGB, and HSL formats. Provide a HEX or RGB color to get equivalent values in all three formats.

Instructions

Convert color between HEX, RGB, and HSL.

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

Input Schema

Name	Required	Description	Default
`color`	Yes	HEX (#FF5733) or RGB (rgb(255,87,51))

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 3, 2026

TDQS

A3.5/5.0

Behavior2/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 mentions conversion between three formats but gives no details on input validation, return format, or error handling. The schema only lists HEX and RGB, creating ambiguity about HSL support, which reduces transparency.

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, front-loaded sentence of just 9 words. It conveys the essential purpose without any filler or redundancy, making it highly concise and well-structured.

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?

The tool is simple with one parameter, but the description is minimal. It does not clarify the HSL inconsistency with the schema, and with no output schema or annotations, it omits details about return values or behavior on invalid inputs. Adequate but with clear gaps.

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 coverage is 100% (the single 'color' parameter is described in the schema). The description adds no parameter-specific information beyond what the schema already provides, so the baseline of 3 is appropriate.

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 uses the specific verb 'Convert' with a clear resource ('color') and explicitly names the three target formats (HEX, RGB, HSL). This fully distinguishes it from sibling conversion tools like convert_currency or convert_units.

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 implied by the clear purpose, but the description does not explicitly state when to choose this tool over alternatives or provide any exclusions. It simply says what it does without contextual guidance.

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