Skip to main content
Glama

QueryMind

Ask about your data

ask

Send a natural-language question to the analysis engine. Reads business data without modifying it, but creates QueryMind query jobs, audit records, conversation context and usage records. Returns an answer, state, limited result rows and evidence. If state=clarifying_question, ask the user the returned question before calling clarify.

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": {
      "question": "<question>"
    },
    "name": "ask"
  }
}

Input Schema

NameRequiredDescriptionDefault
questionYesThe user's natural-language data question; preserve their business meaning.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

The description resolves an otherwise confusing annotation set: although it 'reads business data without modifying it', it explicitly discloses that it creates query jobs, audit records, conversation context and usage records, which explains the readOnlyHint=false. That is exactly the kind of side-effect disclosure annotations cannot carry. It stops short of discussing cost, latency, or rate limits of creating jobs on every call.

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?

Three dense sentences with the core action front-loaded, then side effects, then return shape, then the branching rule. No filler, though the side-effect list is somewhat compressed.

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?

There is no output schema, yet the description enumerates the return payload (answer, state, limited result rows, evidence) and the state-specific follow-up, so an agent knows what to expect and what to do next. The hint that only 'limited result rows' come back is raised but not resolved with a pointer to how to get the full set.

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 coverage is 100% for the single `question` parameter, and the description adds no format, length, or phrasing guidance beyond the schema's own note to preserve business meaning. Baseline 3 applies when the schema already does the work.

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 — 'Send a natural-language question to the analysis engine' — and distinguishes itself from `clarify` by naming the exact state (`clarifying_question`) that routes there. It does not, however, clarify how it relates to other query-adjacent siblings such as `result`, even while mentioning it returns 'limited result rows'.

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?

Gives concrete conditional guidance: when the returned state is `clarifying_question`, the agent must surface the question to the user before calling `clarify`. That is an explicit branch instruction rather than an inference. What is missing is any statement of when to prefer `ask` over alternatives like `explain`, `define`, or `capabilities`.

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