TradeStaq MCP

Official

Overview Schema Source Related Servers Discussions Admin

create_paper_exchange

Create a paper trading exchange with a simulated balance to test strategies, deploy bots, and trade without risking real money. No API keys required.

Instructions

Create a paper-trading exchange with a simulated balance. No API keys required. Paper exchanges let agents test strategies, deploy bots, and place trades without risking real money. Recommended starting point for first-time users and any scope=mcp:paper workflow.

Requires OAuth scope mcp:paper or mcp:live. Session-cookie users (dashboard) can always call this.

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": {
      "platform": "<platform>"
    },
    "name": "create_paper_exchange"
  }
}

Input Schema

Name	Required	Description	Default
`platform`	Yes	Exchange slug, e.g. "binance", "bybit", "okx", "hyperliquid". Use list_exchanges or the web docs for supported options.
`accountLabel`	No	Friendly name shown in dashboard and bot configs, e.g. "BTC Paper Test". Defaults to platform name.
`exchangeType`	No	"spot" for cash trading, "futures" for leveraged/perps.	spot
`initialBalanceUsdt`	No	Simulated starting balance in USDT. Defaults to 10,000.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 4, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Explains no API keys required, simulated balance, no real money. Discloses OAuth scope and session-cookie user access. No annotations provided, so description carries full burden; adequate but could mention rate limits or limits on number of exchanges.

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 paragraphs, front-loaded with purpose and key benefit. No redundant sentences. Efficiently conveys purpose, auth requirements, and usage context.

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?

Fairly complete for a creation tool. Could mention what the response contains (e.g., exchange ID, status) since no output schema exists, but the use case is clear enough for agent invocation.

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

Parameters4/5

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

Schema coverage is 100%. Description adds meaningful examples (e.g., 'binance' for platform, 'BTC Paper Test' for accountLabel) and clarifies enum values (spot vs futures). Justifies baseline 3 plus extra value.

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 it creates a paper-trading exchange with simulated balance. Distinguishes from siblings like connect_exchange (presumably live). Recommends for first-time users and paper workflows.

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?

Recommends as starting point for first-time users and paper workflows. Mentions auth scope requirements. Does not explicitly state when not to use or compare to alternatives, but context from sibling names implies connect_exchange for live.

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