Skip to main content
Glama
Sign In
tool-mcp-server

tool-mcp-server

by maple-awa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

tool_color

Convert any color to HEX, RGB, and HSL values. Input a color name or code to receive all three formats.

Instructions

[utility] Color

Parameters:

  • color (string): Color

Outputs:

  • hex (string): HEX

  • rgb (json): RGB

  • hsl (json): HSL

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "tool_color"
  }
}

Input Schema

NameRequiredDescriptionDefault
hexNoHEX
hslNoHSL
rgbNoRGB
colorNoColor

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.5/5.0
Behavior1/5

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

No annotations exist, so the description must fully disclose behavior. It fails to explain what operation is performed, what color formats are accepted as input, how conversion works, or how errors are handled. The parameter/output listing adds no behavioral context beyond the schema.

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

Conciseness2/5

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

The description is very short and uses a clean list format, but it is under-specified rather than concise. It repeats schema information and omits essential operational details, so each line does not meaningfully earn its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the simple utility context, the lack of an output schema and annotations, and minimal schema descriptions, the description is grossly incomplete. The agent cannot infer the actual conversion logic, accepted input formats, or edge cases, making it insufficient 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?

The schema already has 100% coverage with trivial descriptions (e.g., 'Color', 'HEX'). The description adds only the grouping of 'color' as input and the three as outputs, which is implicit but not explicit in the schema. However, it does not clarify formats, allowed values, or relationships between parameters beyond that.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is just '[utility] Color' with parameter/output lists, lacking an explicit verb or action. It implies a color conversion utility (input color, outputs hex/rgb/hsl), but never states 'convert' or 'parse'. It is distinguishable from siblings only by its name, not by a clear operational statement.

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

Usage Guidelines1/5

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

No guidance is provided on when to use this tool, what problem it solves, or when to choose alternatives. There are no usage conditions, prerequisites, or exclusions; the description is a bare label and data list.

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

Deploy Server

Other Tools