Skip to main content
Glama
mcp-feature-test

mcp-feature-test

by linuxrrze

Ask the user for a colour (MCP App)

pick_color
Read-only

Open a colour picker to ask the user a question, optionally with opacity, returning a hex value (#rrggbb or #rrggbbaa); the answer arrives as a chat message or via pick_color_result.

Instructions

Show a colour picker (MCP App) that asks the user a question; the user may also choose an opacity (the answer is then #rrggbbaa). The call returns immediately; the user answers afterwards. The answer reaches you as a chat message or model context, or call pick_color_result to read it.

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

Input Schema

NameRequiredDescriptionDefault
promptNoQuestion shown above the picker
initialNoPre-selected colour, #rrggbb or #rrggbbaa (alpha)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=true, so the description carries the burden and does so well: it discloses that this is a non-blocking UI call, that the user responds asynchronously, and that the answer may arrive via chat message, model context, or a separate pick_color_result call. That is exactly the kind of behavioral fact an agent cannot infer from the annotations or schema.

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?

Three short sentences, front-loaded with the action, then the async contract, then the retrieval path. No filler and no repetition of the schema.

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 no-output-schema, two-optional-parameter UI tool, the definition covers what an agent needs: it is non-blocking and the answer must be retrieved elsewhere. The only mild gap is not stating whether repeated calls open multiple concurrent pickers.

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 both parameters are already documented in structured form, making 3 the baseline. The description adds only that the answer may include alpha when the user opts into opacity, which is closer to output-format information than parameter guidance.

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?

States a specific verb and resource ("Show a colour picker (MCP App) that asks the user a question") plus the optional opacity capability, which is enough to distinguish it from pick_color_result and pick_color_submit among the siblings.

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

Usage Guidelines4/5

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

Explains the interaction model clearly (returns immediately, user answers afterwards) and routes to the alternative pick_color_result for retrieving the answer. It does not give explicit when-not-to-use guidance versus the other elicitation/dialog siblings, but the context that would drive such a choice is present.

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