Skip to main content
Glama
mcp-feature-test

mcp-feature-test

by linuxrrze

Read the colour picker answer

pick_color_result
Read-only

Retrieve the result of a color-picking request, including the chosen color, cancellation, or pending state; defaults to the most recent request when no ID is provided.

Instructions

Return the answer to a pick_color question: the colour, "cancelled", or "still waiting". Without requestId the most recent pick_color request is used.

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

Input Schema

NameRequiredDescriptionDefault
requestIdNorequestId from pick_color (default: the latest)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4.3/5.0
Behavior4/5

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

readOnlyHint=true is consistent with a pure read. Beyond the annotation, the description adds real behavioral information by disclosing that the call is non-blocking and can return a pending ("still waiting") or user-aborted ("cancelled") state rather than only a colour. It does not say whether multiple outstanding requests are ordered or how long a pending state persists.

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 with the outcome set front-loaded and the default-request fallback second; no padding or redundant explanation.

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

Completeness5/5

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

With no output schema and a single optional parameter, the description carries the return-value burden itself and does so by naming all three terminal states. Nothing an agent needs to call and interpret the result is missing.

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% and the sole parameter's schema description already documents the requestId and its "latest" default, so the description largely restates it. It adds only the framing that the id comes from pick_color, which the schema already conveys.

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 ("return the answer to a pick_color question") and enumerates the three possible results (colour, "cancelled", "still waiting"), which cleanly separates it from the initiating sibling pick_color and from pick_color_submit.

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?

The description makes clear this is the read side of a pick_color interaction and that omitting requestId falls back to the most recent request, which is exactly the guidance needed to invoke it. The "still waiting" outcome implies polling, but it never explicitly says to re-call until resolved or when not to use it.

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