Skip to main content
Glama

QueryMind

Get a pending answer

result
Idempotent

Retrieve the answer, state, limited result rows and evidence for the job_id returned by ask or clarify with state=pending. Completing retrieval can record QueryMind usage; business data remains read-only.

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": {
      "job_id": "<job_id>"
    },
    "name": "result"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYesThe job_id returned by ask or clarify.

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?

Annotations declare readOnlyHint=false, which would otherwise look surprising for a retrieval tool; the description resolves this by explaining that completing retrieval can record QueryMind usage while business data remains read-only. That is exactly the kind of side-effect disclosure annotations cannot carry.

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?

Two sentences, front-loaded with what is retrieved and followed by the side-effect caveat. No filler, no restatement of the title.

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?

With no output schema, the description usefully names the returned components (answer, state, result rows, evidence). It leaves open how "limited" result rows behave—whether truncation or pagination applies—which is the one gap for a polling tool of this shape.

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?

Schema coverage is 100% and the single parameter is documented, so the baseline is 4. The description adds meaning by tying job_id to its origin (a prior ask or clarify call with state=pending), which tells the agent where the value must come from rather than reusing an arbitrary id.

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?

States a specific verb ("Retrieve") and enumerates the returned resources (answer, state, result rows, evidence), then anchors the tool to the job_id produced by ask or clarify with state=pending. This is enough for an agent to distinguish it from ask, clarify, and review without opening a 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?

Gives a clear triggering condition: call this after ask/clarify when the returned state is pending. It does not spell out what to do in other states (e.g., whether the job is finished or failed), but the when-to-use context is explicit rather than implied.

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