Skip to main content
Glama

Agent Data Tools: Full list (every tool as its own definition)

Hex to RGB, color converter: convert a color between hex, RGB and HSL

color
Read-only

Convert a colour between hex, RGB and HSL, and give its relative luminance and whether black or white text reads better on it. Accepts #rgb, #rrggbb, rgb(r,g,b) and hsl(h,s%,l%). Use for theming and design checks. Example: color=#0f6cbd. Price $0.01/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

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

Input Schema

NameRequiredDescriptionDefault
colorYesThe colour

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false. The description reinforces that with 'Reads or computes only and changes nothing' and adds genuinely new context: per-call pricing ($0.01 via x402 USDC or card key), first 25 free, failed calls free, and that repeat calls are not free. It does not explain the output shape, but the pricing/cost behavior the agent needs before calling is disclosed. The 'repeats are not free' line loosely explains the non-idempotent hint.

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?

Front-loaded with the core purpose and accepted formats; the pricing sentence is utilitarian rather than filler. Slight redundancy between 'Reads or computes only and changes nothing' and the charging clause, but nothing is wasted.

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?

For a single-parameter pure-computation tool with a fully covered schema and no output schema, the description covers inputs, the outputs produced (luminance, text recommendation), cost model, and safety profile. The only meaningful gap is how it relates to the overlapping color_contrast sibling.

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?

Schema coverage is 100%, but the schema description is only 'The colour', so the description's enumeration of accepted syntaxes (#rgb, #rrggbb, rgb(r,g,b), hsl(h,s%,l%)) plus a concrete example color=#0f6cbd adds real meaning beyond the schema. It stops short of detailing error behavior for malformed input.

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 transformation (convert a colour between hex, RGB and HSL) plus the additional outputs it returns (relative luminance and black/white text recommendation). The accepted input formats are spelled out. It does not distinguish itself from the sibling color_contrast, which appears to overlap with the luminance/legibility capability, so it falls short of a 5.

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?

'Use for theming and design checks' gives only implied usage context, with no explicit when-to-use/when-not guidance and no mention of the obvious alternative (color_contrast) for contrast-specific work. An agent can infer the fit, but must guess at the boundary.

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.