Skip to main content
Glama
tradeparadex

Paradex MCP Server

by tradeparadex

Order Status

paradex_order_status
Read-onlyIdempotent

Check the detailed status of a specific order to confirm execution, fill status, or diagnose issues with order placement.

Instructions

Check the detailed status of a specific order for execution monitoring.

Use this tool when you need to:
- Confirm if a particular order was accepted and is active
- Check if an order has been filled, partially filled, or canceled
- Get execution details for a specific order
- Diagnose issues with order placement
- Track the status of important orders individually

Order status tracking is essential for verifying execution status
and troubleshooting any issues with specific orders.

Example use cases:
- Checking if a recently placed limit order is active in the book
- Verifying fill details of a specific order
- Determining why an order might have been rejected
- Confirming cancellation status of an order you attempted to cancel
- Getting execution timestamps for order lifecycle analysis

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
order_idYesOrder identifier.
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
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint. The description adds value by elaborating on behavioral details like execution monitoring, timestamps, and lifecycle analysis, which go beyond the annotations.

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 a clear main sentence followed by bullet-like use cases. It is not overly verbose and each sentence serves a purpose.

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 tool has only 2 required params and an output schema, the description fully covers the tool's purpose, usage context, and examples. No 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?

Schema coverage is 100% with descriptions for both order_id and client_id. The description does not add new parameter information beyond the schema, so baseline 3 is appropriate.

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 checks the detailed status of a specific order for execution monitoring. It distinguishes from siblings like paradex_open_orders (list) and paradex_orders_history (history) by focusing on individual order lookup.

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 provides explicit use cases (confirm acceptance, check fill status, diagnose issues) and example use cases. It does not explicitly state when not to use, but the context is clear.

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