Skip to main content
Glama
tradeparadex

Paradex MCP Server

by tradeparadex

Create Order

paradex_create_order
Destructive

Execute trades on Paradex with control over order type, size, price, and execution parameters. Set limit, stop-loss, take-profit, or market orders for risk management.

Instructions

Execute trades on Paradex with precise control over all order parameters.

Use this tool when you need to:
- Enter a new position based on your trading strategy
- Set limit orders at specific price levels
- Create stop-loss or take-profit orders for risk management
- Implement complex trading strategies with conditional orders

This is the primary tool for executing your trading decisions on Paradex,
with full control over order type, size, price, and execution parameters.

Example use cases:
- Setting limit orders at key support/resistance levels
- Placing stop-limit orders to manage risk on existing positions
- Executing market orders for immediate entry or exit
- Creating reduce-only orders to ensure you don't flip position direction

Succesful response indicates that orders were queued for execution.
Check order status using order id.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
market_idYesMarket identifier.
order_sideYesOrder side.
order_typeYesOrder type.
sizeYesOrder size.
priceYesOrder price (required for LIMIT orders).
trigger_priceYesTrigger price for stop limit orders.
instructionNoInstruction for order execution.GTC
reduce_onlyNoReduce-only flag.
client_idYesClient-specified order ID.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
accountNoParadex Account
avg_fill_priceNoAverage fill price of the order
cancel_reasonNoReason for order cancellation if it was closed by cancel
client_idNoClient order id provided by the client at order creation
created_atNoOrder creation time
flagsNoOrder flags, allow flag: REDUCE_ONLY
idNoUnique order identifier generated by Paradex
instructionNoExecution instruction for order matching
last_updated_atNoOrder last update time. No changes once status=CLOSED
marketNoMarket
priceNoOrder price. 0 for MARKET orders
published_atNoTimestamp in milliseconds when order was sent to the client
received_atNoTimestamp in milliseconds when order was received by API service
remaining_sizeNoRemaining size of the order
request_infoNoAdditional request information for orders
seq_noNoUnique increasing number (non-sequential) that is assigned to this order update and changes on every order update. Can be used to deduplicate multiple feeds. WebSocket and REST responses use independently generated seq_no per event.
sideNoOrder side
sizeNoOrder size
statusNoOrder status
stpNoSelf Trade Prevention mode
timestampNoOrder signature timestamp
trigger_priceNoTrigger price for stop order
typeNoOrder type
Behavior5/5

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

Beyond the annotations (destructiveHint: true), the description adds valuable behavioral context: successful response means orders are queued for execution, not immediately filled, and recommends checking order status using order ID. It also notes different order types like reduce-only for risk management.

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?

The description is well-structured with bullet points and sections, and it front-loads the main purpose. It is around 150 words; while efficient, some example use cases could be condensed further.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity (9 parameters, 7 required, enums, output schema), the description covers what the agent needs: how to interpret success (queued, not filled), where to check status, and typical use cases. No major gaps remain.

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?

The input schema has 100% description coverage, so the schema already documents each parameter. The description adds no extra parameter-specific details beyond the general statement of 'precise control.' Baseline 3 is appropriate as the description does not enhance parameter understanding.

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?

The description clearly states the tool's purpose: 'Execute trades on Paradex with precise control over all order parameters.' It distinguishes itself as the primary tool for order execution among many related sibling tools, providing specific use cases and examples.

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?

The description explicitly lists when to use this tool (entering positions, limit orders, stop-loss, etc.) but does not explicitly state when not to use it or suggest alternative tools. This is a minor omission given the clear context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/tradeparadex/mcp-paradex-py'

If you have feedback or need assistance with the MCP directory API, please join our Discord server