Skip to main content
Glama

Ask question

ask_question
Read-only

Ask the user a structured multiple-choice question to resolve a genuine ambiguity. Use this when the user's request is missing information you cannot infer (which of several clusters, which of several namespaces, which of several charts) and getting the answer would save more than two tool calls of guessing. Do NOT use for questions you can answer from cluster_query, the page context, or a single sensible default. Hard cap of 2 calls per turn. After calling, end the turn and wait for the user's reply in the next message.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "questions": "<questions>"
    },
    "name": "ask_question"
  }
}

Input Schema

NameRequiredDescriptionDefault
questionsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

The readOnlyHint annotation is consistent, but the description goes well beyond it: it discloses the throttling behavior (hard cap of 2 calls per turn) and the required control-flow after invocation (end the turn, wait for the reply in the next message). Those are the exact behaviors an agent could not infer from the annotations or schema and would otherwise get wrong.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Roughly four sentences, front-loaded with the purpose, then the use condition, then the exclusion, then the operational constraints. Every sentence contributes; the minor cost is that the exclusion clause is packed into one long sentence that has to be parsed carefully.

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 1-parameter interaction tool with no output schema, the description covers purpose, gating conditions, rate limits, and what happens after the call. The only gap is that the shape of the user's answer (structured option ids or free text) is implied rather than stated, which matters when the caller must interpret the reply.

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 reported at 0%, so the description carries the burden of explaining the single nested 'questions' parameter, and it only partially does so via the examples ('which of several clusters, which of several namespaces, which of several charts'). It never mentions the undocumented levers the schema exposes: allow_multiple, the 3-question / 12-option caps, or the 480/200 character limits, so an agent still has to read the schema to use the parameter fully.

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?

The description names a specific verb and resource ('Ask the user a structured multiple-choice question') and immediately scopes it to 'resolve a genuine ambiguity'. That framing alone lets an agent distinguish it from every sibling data-fetching tool in the list, none of which pause for user input.

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

Usage Guidelines5/5

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

It gives an explicit when-to-use test ('missing information you cannot infer... would save more than two tool calls of guessing'), an explicit when-not-to-use list ('questions you can answer from cluster_query, the page context, or a single sensible default'), and names those alternatives directly. The hard cap of 2 calls per turn and the instruction to end the turn add the operational boundaries a caller needs.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.