Skip to main content
Glama
Sign In
TradeStaq MCP

TradeStaq MCP

Official
by the-staq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

export_bot_trades

Export trade history as structured data with PnL, entry/exit prices, and performance summary for analysis.

Instructions

Export a bot's trade history as structured data. Returns all trades with PnL, entry/exit prices, and performance summary.

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": {
      "id": "<id>"
    },
    "name": "export_bot_trades"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesBot ID
formatNosummary = stats + recent trades, full = all tradessummary

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It does not disclose side effects, file generation, permissions, or whether the tool is read-only. The term 'Export' may imply file download but is not clarified.

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 with no wasted words. Front-loaded with the core action and follow-up on return content.

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?

The description covers the basic purpose and return data but lacks details on output format, pagination, or any limitations. For a simple tool with no output schema, it is adequate but not thorough.

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 is 3. The description adds some context about returned data (PnL, prices, summary) but does not elaborate on parameter behavior beyond what the schema covers.

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 clearly states the tool exports a bot's trade history as structured data, mentioning specific elements like PnL and prices. It distinguishes from siblings like export_backtest and get_trade_history, though not explicitly.

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 guidance on when to use this tool versus alternatives such as get_trade_history or export_backtest. The description only states what the tool does without context.

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