Skip to main content
Glama
mcp-feature-test

mcp-feature-test

by linuxrrze

Confirm dialog (elicitation)

elicit_confirm
Read-only

Prompts users with a native yes/no dialog to confirm a simulated destructive action and verifies accept, decline, and cancel handling.

Instructions

Ask the user to confirm a (fake, harmless) destructive action via a native yes/no elicitation dialog. Demonstrates accept / decline / cancel handling.

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

Input Schema

NameRequiredDescriptionDefault
itemNoName of the fake item to "delete"important-file.txt

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description is consistent with them by labeling the destructive action as fake and harmless. It adds real behavioral context beyond the annotations: the dialog is native, it is yes/no, and the caller should expect accept/decline/cancel outcomes to be handled. It does not describe what is returned for each outcome in detail, but the enumeration of outcomes is the key signal.

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 short sentences, zero filler, with the core action front-loaded and the demonstration purpose immediately after. Nothing needs trimming.

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 single-optional-param demo tool with no output schema, the description supplies what an agent needs: that it is an elicitation dialog, that it is harmless, and which response outcomes to expect. A brief note on what the response payload looks like would close the remaining gap, but the definition is broadly sufficient.

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% and the single optional parameter has a documented default, so the schema carries the load. The description never mentions the item parameter or the fact that the item name is cosmetic; baseline 3 applies.

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: asking the user to confirm via a native yes/no elicitation dialog. The parenthetical "(fake, harmless) destructive action" makes clear this is a demo rather than a real deletion. It does not explicitly contrast with sibling elicitation tools like elicit_all_field_types or elicit_wizard, leaving differentiation to the reader.

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

Usage Guidelines3/5

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

"Demonstrates accept / decline / cancel handling" implies this is a demonstration/probe tool rather than something to use in production flows, and the yes/no framing suggests when it applies. However, there is no explicit statement of when to prefer it over the other elicit_* siblings or what preconditions exist.

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