Skip to main content
Glama
mcp-feature-test

mcp-feature-test

by linuxrrze

Two dialogs in one round (elicitation)

elicit_parallel
Read-only

Requests two independent user elicitations in one input_required round to test how clients handle multiple pending input prompts, showing them together or sequentially.

Instructions

Request two independent elicitations in a single input_required round. Tests how a client handles several pending input requests (modern clients may show them together; legacy clients one after the other).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.9/5.0
Behavior3/5

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

Annotations declare only readOnlyHint=true, so the description carries most of the behavioral burden. It usefully discloses that the call triggers an input_required round with two concurrent prompts and that client presentation varies, but it does not say what comes back or how partial/abandoned input is handled.

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, front-loaded with the core action, and the parenthetical adds genuinely useful client-behavior information rather than filler.

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?

With zero parameters, a trivial schema, and no output schema, the definition covers what an agent needs to decide to call it. The remaining gap is the shape of the returned elicitation results, which the description never touches.

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?

The tool takes zero parameters, so there is no parameter meaning to compensate for; the baseline for a parameterless schema applies. The description correctly implies no inputs are needed.

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?

The description gives a specific action (request two independent elicitations in one input_required round), which clearly distinguishes it from single-elicitation siblings such as elicit_confirm or elicit_url. It stops short of explicitly naming a sibling it replaces, but the scope is unambiguous.

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?

It states the context in which the tool is appropriate, namely probing how a client handles several simultaneously pending input requests, and notes modern vs legacy client behavior. It offers no explicit when-not-to-use condition or named alternative probe.

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