TradeStaq MCP

Official

Overview Schema Source Related Servers Discussions Admin

get_trade_history

Retrieve closed trade history with PnL, entry/exit prices, and duration. Filter by symbol or exchange and paginate results.

Instructions

Get your closed trade history with PnL, entry/exit prices, and duration.

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

Input Schema

Name	Required	Description
`page`	No	Page number for pagination
`limit`	No	Number of trades to return (max 200)
`symbol`	No	Filter by trading pair symbol
`exchange`	No	Filter by exchange name

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 4, 2026

TDQS

B3.1/5.0

Behavior2/5

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

No annotations provided, so description must carry burden. Mentions output content but does not disclose authentication needs, side effects (read-only), rate limits, or behavior when no trades exist.

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?

Single sentence that is front-loaded with purpose and key data points. Efficient but lacks structure (e.g., bullet points or examples).

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?

No output schema and no annotations. Description is minimal and does not cover return format, pagination behavior, error handling, or edge cases given complexity of sibling tools.

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 baseline 3. Description adds no extra meaning beyond schema parameter descriptions. Does not elaborate on parameter usage or formatting.

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?

Clearly states the verb 'Get', resource 'closed trade history', and included data (PnL, entry/exit prices, duration). Distinguishes from sibling tools like get_positions.

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 explicit guidance on when to use this tool versus alternatives (e.g., get_positions for open trades). No when-not-to-use or exclusions.

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