lxDIG MCP

decision_query

Query past decision episodes for a given topic, filtered by task or agent, to retrieve relevant context and reasoning.

Instructions

Query decision episodes for a target topic

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": {
      "query": "<query>"
    },
    "name": "decision_query"
  }
}

Input Schema

Name	Required	Description	Default
`query`	Yes	Decision query text
`affectedFiles`	No	Related files/entities
`taskId`	No	Task filter
`agentId`	No	Agent filter
`limit`	No	Result limit
`profile`	No	Response profile	compact

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Jun 21, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are supplied, and the description does not disclose behavioral traits such as whether the tool is read-only, idempotent, or has side effects. It does not mention authentication, rate limits, or what triggers the query.

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?

The description is a single, short sentence with no wasted words. It is appropriately concise but could benefit from a bit more detail without harming conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With six parameters, one required, and no output schema, the description is insufficient. It does not explain what 'decision episodes' are, how results are returned, or how to interpret the response. This leaves the agent with significant ambiguity.

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%, so the baseline is 3. The description adds no additional meaning beyond the schema's parameter descriptions. It does not clarify how parameters relate to the query or their semantic roles.

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?

The description clearly states the action 'Query' and the resource 'decision episodes' for a target topic, which distinguishes it from some siblings like progress_query. However, it lacks explicit differentiation from similar query tools such as ref_query or episode_recall.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives, nor any prerequisites or exclusions. The description solely states the action without contextual usage advice.

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