MCP-Confirm
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ask_yes_noA | Ask a yes/no confirmation question to the user when the AI needs clarification or verification |
| confirm_actionB | Ask user to confirm an action before proceeding with potentially impactful operations |
| clarify_intentA | Ask user to clarify their intent when the request is ambiguous or could be interpreted multiple ways |
| verify_understandingC | Verify that the AI correctly understood the user's requirements before proceeding |
| collect_ratingC | Collect user satisfaction rating for AI's response or help quality |
| elicit_customA | Create a custom confirmation dialog with specific schema when standard tools don't fit |
| search_logsC | Search confirmation history logs with various filters and pagination |
| analyze_logsC | Perform statistical analysis on confirmation history logs |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Each tool has a clearly distinct purpose with no ambiguity. For example, ask_yes_no handles simple binary questions, clarify_intent addresses ambiguous requests, confirm_action verifies impactful operations, and verify_understanding checks comprehension—all serving different confirmation needs without overlap.
All tools follow a consistent verb_noun pattern with clear, descriptive names. Examples include analyze_logs, search_logs, collect_rating, and verify_understanding, maintaining uniformity throughout the set without any deviations in style or structure.
With 8 tools, the server is well-scoped for handling user confirmation and verification tasks. Each tool earns its place by covering distinct aspects like questioning, clarification, logging, and feedback, avoiding both bloat and insufficiency.
The tool set provides complete coverage for the confirmation domain, including standard confirmations (ask_yes_no, confirm_action), intent handling (clarify_intent, verify_understanding), feedback collection (collect_rating), logging (analyze_logs, search_logs), and customization (elicit_custom), with no apparent gaps.