Skip to main content
Glama

analyze_decision

Read-onlyIdempotent

Adversarially audit a decision for cognitive biases. Returns a directive YOUR model executes to produce the composed audit (verdict-first). Provide reasoning, not just the conclusion.

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": {
      "judgment": "<judgment>"
    },
    "name": "analyze_decision"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNoforward = a decision you are about to make; retrospective = reviewing a past decision/outcome.
judgmentYesThe decision/judgment in one line.
languageNoOptional. Natural language for the audit prose (e.g. "Tamil", "Spanish"). Bias ids stay canonical English so the result is still parseable. Defaults to English.
reasoningNoHow you arrived at it (required to audit).
structuredNoOptional. Default false → the audit comes back as readable prose. Set true to get a machine-parseable JSON object (bias ids/keys in English) for pipelines that store or compare audits.

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 establish readOnly/idempotent/non-destructive, but the description adds genuinely non-obvious behavior: the tool returns a directive the caller must execute, the output is verdict-first, and it switches between prose and machine-parseable JSON. That is real value beyond the structured fields, though it doesn't cover failure modes or output size.

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, all front-loaded: what it does, the unusual directive-execution contract, and the input requirement. No filler, and the most surprising fact (the model, not the tool, composes the audit) appears early.

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 five params, no output schema, and only one required field, the description does the heavy lifting on return shape (prose vs JSON) that the missing output schema would otherwise need. The exact JSON structure returned when structured=true is left unspecified, which is the remaining gap.

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 mode, language, judgment and structured are already documented in the schema. The description only reinforces that reasoning is mandatory for a usable audit; it adds no syntax or format detail beyond what the schema provides.

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 names a specific verb and resource ('adversarially audit a decision for cognitive biases') and clarifies the unusual mechanic that the tool returns a directive the calling model executes rather than performing the audit itself. It does not explicitly contrast with the sibling lookup tools get_bias/list_biases, so it stops short of a 5.

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?

It states a requirement ('provide reasoning, not just the conclusion') and hints at the forward/retrospective split, but it never says when to reach for this tool versus get_bias or list_biases, nor when an audit is inappropriate. Usage is implied rather than spelled out.

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.