Ask Question MCP App
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| submit_answerC | Submit an answer to a pending question. Used internally by the question UI. |
| ask_questionA | Ask the user a question with an interactive UI. Supports text input, single/multi-select options, and yes/no confirmation dialogs. Waits for user response and returns the answer. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Question UI | Interactive question form UI |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: ask_question initiates a question to the user with UI support, while submit_answer handles the response submission. There is no overlap or ambiguity between them, as one is for asking and the other for answering.
Both tools follow a consistent verb_noun pattern (ask_question and submit_answer), using snake_case throughout. The naming is predictable and aligns well with their functions, with no deviations or mixed conventions.
With only 2 tools, the set feels thin for a server named 'Ask Question MCP App', which suggests a broader interactive questioning domain. This minimal count may limit functionality, as agents might expect more features like managing questions or handling different dialog types beyond the basic ask-answer cycle.
The tool surface is significantly incomplete for an interactive questioning domain. While ask_question and submit_answer cover a basic ask-answer flow, there are notable gaps such as tools for listing pending questions, canceling questions, or handling different UI modes beyond the described ones. This could lead to agent failures in more complex scenarios.