Skip to main content
Glama

QueryMind

Answer a clarification

clarify

Continue the previous ask after the engine requests clarification. May create a QueryMind query job and update audit records, conversation context and usage records; business data remains read-only. Send the user's choice or additional explanation; do not invent their choice.

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": {
      "choice": "<choice>"
    },
    "name": "clarify"
  }
}

Input Schema

NameRequiredDescriptionDefault
choiceYesThe user's choice or additional explanation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations by enumerating side effects: a possible QueryMind query job, audit records, conversation context and usage records are written, while business data stays read-only. This makes clear the call is stateful and may kick off work, which the readOnlyHint=false and idempotentHint=false alone would not convey.

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?

Three short sentences: trigger first, side effects second, argument rules last. Every clause carries operational information and there is no 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?

For a stateful continuation tool with no output schema, the definition covers the trigger, the writes it performs and the argument constraint. What the call returns and how the conversation flow resumes afterwards is left implicit, which is a minor gap rather than a blocking one.

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?

With one parameter at full schema coverage the baseline is 3, but the description adds real meaning by requiring the value be the user's own choice or explanation and warning against fabricating it. That is a behavioral constraint on the argument, not a restatement of the schema text.

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 states a specific action (continue the previous ask) tied to a specific trigger (the engine requested clarification), which cleanly separates it from the sibling 'ask' that starts a new request. An agent can tell which tool to call without inspecting the schema.

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?

The trigger condition is explicit and actionable: use this only after a clarification request from the engine, and it must carry the user's actual choice. No sibling alternatives are named, but the precondition is clear enough that misuse is unlikely.

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.

Resources