Skip to main content
Glama

QueryMind

Explain an answer's basis

explain
Read-onlyIdempotent

Show the data source, query conditions (SQL), time basis and access restrictions for a recent answer accessible to this connection.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "explain"
  }
}

Input Schema

NameRequiredDescriptionDefault
audit_idNoOmit to explain the most recent ask answer.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare this as a safe, idempotent, closed-world read, so the description isn't carrying the safety burden. It does add real behavioral context: the return content is enumerated (source, SQL, time basis, restrictions) and access is scoped to "this connection," which tells the agent results may be permission-filtered. It stops short of noting retention limits or behavior on a stale/unknown audit_id.

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?

One sentence, front-loaded with the verb and the enumerated outputs, with no redundant restatement of the title. Every clause contributes either scope or return content.

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 one-optional-parameter read tool with no output schema, the description covers what the response contains and the access boundary, which is what an agent needs to decide to call it. Minor gaps remain around the meaning of 'recent' and error behavior for an inaccessible audit_id.

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% and the single parameter already documents the omit-to-default behavior. The description reinforces the "recent answer" framing but adds no new syntax, range, or format detail beyond the schema. Baseline 3 is appropriate since the schema 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?

Uses a specific verb ("Show") with a precisely enumerated payload: data source, query conditions (SQL), time basis, and access restrictions for one answer. That is far more concrete than the sibling names 'result' or 'ask' imply, though the description never names an alternative tool to disambiguate against them. Clear purpose, but differentiation must be inferred.

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

Usage Guidelines3/5

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

Usage is only implied through scope phrases like "a recent answer accessible to this connection" and, in the schema, "omit to explain the most recent ask answer." There is no explicit statement of when to choose this over 'result' or 'ask', and no stated failure conditions (e.g., what happens for an out-of-scope audit_id). Adequate but the agent must infer the routing.

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