TradingAgents MCP

Overview Schema Source Related Servers Discussions Admin

list_reports

Retrieve saved stock and crypto analysis reports newest first, including ticker, date, and rating from both engines; use read_report to open a specific report.

Instructions

List saved analysis reports, newest first, from both engines (the trading-analysis skill and the API pipeline), with ticker, date and rating. Read one with read_report.

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

Input Schema

Name	Required	Description	Default
`limit`	No
`ticker`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Nov 7, 2026

TDQS

A3.8/5.0

Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does add real behavioral context — result ordering, that results span two distinct sources, and which fields come back — but it omits pagination/truncation behavior, whether limit caps results silently, and whether ticker matching is exact or partial. Adequate disclosure for a read-only listing, but not complete.

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?

Two sentences, zero filler, with the core scope and ordering front-loaded and the follow-up action placed last. Every clause carries 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 (the description covers them anyway), and the read-only nature is implicit. However, for a two-parameter filtering tool with no annotations and 0% schema coverage, the missing parameter semantics leave a real gap an agent would notice when trying to use the ticker filter.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and both parameters (limit, ticker) are undocumented in the schema. The description never explains that ticker filters results or what limit does or its default; "with ticker, date and rating" reads as return fields, not parameter behavior. With low schema coverage, the description should compensate and does not.

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 and resource ("List saved analysis reports") plus ordering ("newest first"), scope ("both engines" — names the trading-analysis skill and API pipeline), and returned fields. It is immediately distinguishable from read_report, which it explicitly names as the retrieval counterpart.

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

Usage Guidelines4/5

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

Explicitly routes the agent: use this to browse, then "Read one with read_report." That is clear when-to-use plus a named alternative. It lacks any when-not guidance (e.g., that this cannot fetch report content or filter by date), which keeps it below a 5.

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