Skip to main content
Glama
tradeparadex

Paradex MCP Server

by tradeparadex

Open Orders

paradex_open_orders
Read-onlyIdempotent

Retrieve your active orders to monitor execution status and manage trading strategy. Check pending orders, verify limit prices, and assess market exposure.

Instructions

Monitor your active orders to track execution status and manage your trading strategy.

Use this tool when you need to:
- Check which of your orders are still pending execution
- Verify limit order prices and remaining quantities
- Determine which orders might need cancellation or modification
- Get a complete picture of your current market exposure

Keeping track of your open orders is essential for effective order management
and avoiding duplicate or conflicting trades.

Example use cases:
- Checking if your limit orders have been partially filled
- Verifying that a recently placed order was accepted by the exchange
- Identifying stale orders that should be canceled or modified
- Getting a consolidated view of all pending orders across markets

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
market_idNoFilter by market.ALL
limitNoLimit the number of results to the specified number.
offsetNoOffset the results to the specified number.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultsYes
totalYes
limitYes
offsetYes
Behavior3/5

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

Annotations already provide readOnlyHint=true and idempotentHint=true. The description adds that the tool is for monitoring and managing orders, which aligns but does not significantly expand beyond the annotations. No contradictions.

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 example use cases, but it is slightly verbose. It could be more concise without losing clarity, but it is not overly long.

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?

Given the high schema coverage, informative annotations, and presence of an output schema, the description covers the purpose and usage adequately. Example use cases add completeness, though it could benefit from mentioning the default market_id behavior.

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 parameters are fully documented in the schema. The description does not add parameter-specific details beyond what is already in the schema, earning a baseline 3.

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 uses specific verbs like 'monitor', 'check', 'verify', 'determine', and 'get' tied to a clear resource ('active orders'). It distinguishes from siblings such as paradex_order_status and paradex_orders_history by focusing on pending orders across markets.

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: checking pending orders, verifying prices/quantities, determining cancellation need, and getting market exposure. It does not mention when not to use or explicitly name alternatives, 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