TradingAgents MCP

Overview Schema Source Related Servers Discussions Admin

past_decisions

Retrieve historical trading decisions with realized returns, alpha, and reflections, optionally filtered by ticker, to evaluate outcomes and guide new trades.

Instructions

The raw memory log: past decisions and, once settled, their realised return, alpha and reflection. Optionally filtered to one ticker.

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": "past_decisions"
  }
}

Input Schema

Name	Required	Description	Default
`ticker`	No
`max_chars`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Nov 7, 2026

TDQS

B3.3/5.0

Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It discloses useful content shape (settled entries carry realised return, alpha and reflection) but says nothing about read-only semantics, ordering, or that output may be truncated to max_chars — a material behavior for a log tool with a 20,000-character default.

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 compact sentence that front-loads the identity of the resource and then the optional filter. Nothing is redundant and no sentence fails to add information.

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

Completeness3/5

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

An output schema exists, so return values need not be described, and the description correctly states the record contents. However, truncation behavior and routing relative to the closely related memory_lessons and unsettled_decisions tools are missing, leaving gaps for a tool with unannotated parameters.

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 0% for two parameters. The description covers the optional ticker filter ('one ticker') but leaves max_chars entirely unexplained, so an agent cannot tell from the definition that it controls output truncation or what happens when the log exceeds it.

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 concrete resource ('the raw memory log') and enumerates what it contains: past decisions plus, once settled, realised return, alpha and reflection. That distinguishes it implicitly from memory_lessons and unsettled_decisions, but it never names those siblings, so the differentiation requires inference.

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?

The only usage guidance is 'Optionally filtered to one ticker', which tells the agent how to narrow results but not when to reach for this tool over unsettled_decisions (open decisions only) or memory_lessons (distilled lessons). Usage is implied by the resource name rather than stated.

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