Skip to main content
Glama
mcp-feature-test

mcp-feature-test

by linuxrrze

Submit colour picker answer (app-only)

pick_color_submit

Stores the user's color picker response (accept or cancel) so the client can submit a selection or cancellation for a pending request.

Instructions

Called by the colour picker UI to store the user's answer (OK or Cancel). Hidden from the model.

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": {
      "requestId": "<requestId>",
      "action": "<action>"
    },
    "name": "pick_color_submit"
  }
}

Input Schema

NameRequiredDescriptionDefault
colorNo
actionYes
requestIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.5/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 behavioral burden, and it does disclose the key trait: this is a UI-invoked callback, not a model-facing tool. However, it says nothing about what happens on an unknown or stale requestId, whether the pending picker resolves, or what the call returns. It also paraphrases the action values as 'OK or Cancel' while the schema enum is 'accept'/'cancel', a terminology mismatch that could confuse a reader.

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?

Two sentences, no filler, and the caller identity is front-loaded before the model-hiding constraint. Every clause earns its place.

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 three-parameter callback with no annotations and no output schema, the description covers the most important fact (do not call this) but not the parameter semantics an implementer would need. It is adequate for a model deciding not to use it, and thin for anyone actually wiring up the call.

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 explain all three parameters. It only gestures at 'action' via 'OK or Cancel' and leaves requestId (correlation token) and color (nullable, maxLength 20) entirely unexplained, including what a null color means on cancel.

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 verb and resource — 'store the user's answer' — and names the caller ('the colour picker UI'), which distinguishes it from the picker-opening sibling pick_color. It doesn't explicitly contrast with pick_color_result or dialog_lab_submit, so sibling differentiation is implied by the caller rather than stated.

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?

'Called by the colour picker UI' and 'Hidden from the model' give an explicit when-not-to-use signal: an agent should not invoke this itself. It stops short of naming an alternative for a model that wants to read the stored answer, which is what pick_color_result likely provides.

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