Skip to main content
Glama
putervision

agent-reasoning-mcp

by putervision
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_decision_trace

Read-onlyIdempotent

Retrieve step-by-step reasoning traces, candidate utilities, and risk assessments for past decisions to explain or audit a specific historical choice.

Instructions

Retrieve explainable step-by-step chain-of-thought rationale, candidate utilities, and risk assessment for past decisions (actions: latest, get, list, explain). Use get_decision_trace instead of query_knowledge when performing deep forensic analysis of a specific historical decision.

Returns step-by-step reasoning trace, utility breakdown, candidate rankings, and explanation text.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax traces to list
actionYesTrace retrieval operation: latest, get, list, explain
goal_idNoFilter traces by linked goal ID
projectNoTarget project slug
trace_idNoTrace ID for get/explain action

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.3.1
    • changedInput schema / properties / action / description
      Previous value: -"Trace retrieval operation"New value: +"Trace retrieval operation: latest, get, list, explain"
    • addedInput schema / properties / action / enum
      Added value: +[
+  "latest",
+  "get",
+  "list",
+  "explain"
+]
  2. Changed8 schema fields changedv0.2.1
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / action / description
      Added value: +"Trace retrieval operation"
    • removedInput schema / properties / action / enum
      Removed value: -[
-  "latest",
-  "get",
-  "list",
-  "explain"
-]
    • addedInput schema / properties / goal_id / description
      Added value: +"Filter traces by linked goal ID"
    • addedInput schema / properties / limit / description
      Added value: +"Max traces to list"
    • addedInput schema / properties / project / description
      Added value: +"Target project slug"
    • addedInput schema / properties / trace_id / description
      Added value: +"Trace ID for get/explain action"
  3. First observedv0.1.2

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds value by enumerating the return structure (trace, utility breakdown, candidate rankings, explanation text), which matters since no output schema exists. It does not discuss filtering semantics or limits, keeping it short of a 5.

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?

Two short sentences, purpose front-loaded and the sibling call-out second. The parenthetical action list duplicates the enum and the return enumeration slightly overlaps, but nothing is buried or wasted.

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 helpfully summarizes return values, and annotations carry the safety profile. What is missing is guidance on how action values interact with the other params (which params apply to get vs list), leaving a small gap for a 5-param tool.

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 description coverage is 100%, so all five parameters are already documented, including the action enum. The description only restates the action values parenthetically and adds no syntax or interaction detail (e.g., trace_id required for get/explain), so baseline 3 is correct.

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 resource (decision trace) plus the payload it contains (chain-of-thought rationale, candidate utilities, risk assessment). It explicitly contrasts itself with query_knowledge, so an agent can distinguish it from siblings without schema inspection.

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

Usage Guidelines5/5

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

Names the alternative (query_knowledge) and the precise condition that selects this tool: deep forensic analysis of a specific historical decision. The action set (latest, get, list, explain) further signals usage modes.

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

Deploy Server

Other Tools