CCXT MCP Server

createOrder

Place cryptocurrency buy or sell orders on exchanges by specifying account, symbol, type, side, and amount.

Instructions

Create a new order using a configured account

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": {
      "accountName": "<accountName>",
      "symbol": "<symbol>",
      "type": "<type>",
      "side": "<side>",
      "amount": "<amount>"
    },
    "name": "createOrder"
  }
}

Input Schema

Name	Required	Description
`accountName`	Yes	Account name defined in the configuration file (e.g., 'bybit_main')
`symbol`	Yes	Trading symbol (e.g., 'BTC/USDT')
`type`	Yes	Order type: 'market' or 'limit'
`side`	Yes	Order side: 'buy' or 'sell'
`amount`	Yes	Amount of base currency to trade
`price`	No	Price per unit (required for limit orders)
`params`	No	Additional exchange-specific parameters

Schema Changelog

Changes observed during successful MCP inspections.

First observedAug 18, 2025

TDQS

C2.9/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 of behavioral disclosure. It states 'Create a new order', implying a write/mutation operation, but doesn't disclose critical traits like authentication needs, rate limits, error handling, or what happens on success (e.g., order ID returned). For a financial trading tool with potential real-world consequences, this lack of transparency is a significant gap.

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?

The description is a single, efficient sentence with zero wasted words. It's front-loaded with the core action ('Create a new order') and includes only essential context ('using a configured account'). Every part earns its place, making it highly concise and well-structured for quick comprehension.

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?

Given the complexity of a financial trading tool with 7 parameters, no annotations, and no output schema, the description is incomplete. It lacks crucial context such as authentication requirements, error scenarios, return values (e.g., order ID), and behavioral details like rate limits or idempotency. The schema handles parameter documentation, but the description fails to compensate for missing annotations and output schema.

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 100%, so the schema already documents all 7 parameters thoroughly with descriptions and enums. The description adds no additional meaning beyond the schema, as it doesn't explain parameter relationships (e.g., 'price' required for 'limit' orders) or provide usage examples. The baseline score of 3 reflects adequate parameter documentation solely from the schema.

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 action ('Create a new order') and resource ('using a configured account'), making the purpose unambiguous. It distinguishes from sibling tools like 'cancelOrder' or 'fetchOpenOrders' by focusing on creation rather than modification or retrieval. However, it doesn't specify what kind of order (e.g., trading order) or differentiate from other potential order creation tools that might exist in other contexts.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing a configured account), exclusions (e.g., not for modifying existing orders), or comparisons to siblings like 'cancelOrder' or 'fetchOrder'. The phrase 'using a configured account' hints at a prerequisite but doesn't explicitly state it as a requirement or explain how to configure accounts.

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