Skip to main content
Glama
tradeparadex

Paradex MCP Server

by tradeparadex

Cancel Orders

paradex_cancel_orders
Destructive

Cancel pending orders to manage exposure, remove stale limit orders, or quickly adjust your trading strategy during market volatility.

Instructions

Cancel pending orders to manage exposure or adjust your trading strategy.

Use this tool when you need to:
- Remove stale limit orders that are no longer desirable
- Quickly reduce market exposure during volatility
- Update your order strategy by removing existing orders
- Clear your order book before implementing a new strategy
- React to changing market conditions by canceling pending orders

Order cancellation is a critical risk management function and allows you
to quickly adapt to changing market conditions.

Example use cases:
- Canceling limit orders when your outlook changes
- Removing all orders during unexpected market volatility
- Canceling a specific order identified by order ID
- Clearing all orders for a specific market
- Removing stale orders before placing new ones

Calling without any parameters will cancel all orders.

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
order_idNoOrder id (received from create_order)
client_idNoClient id (provided by you on create_order)
market_idNoMarket is the market to cancel orders forALL

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

Adds key behavioral info beyond destructiveHint: 'Calling without any parameters will cancel all orders' and 'successful response indicates queueing for cancellation'. No inconsistency with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Reasonably structured with sections, but includes some redundancy (e.g., reacting to market conditions mentioned twice in usage list). Could be more concise while retaining essential information.

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?

Covers critical behaviors (all-cancel default, queued response, post-cancel check). Output schema exists so return details not needed. Minor gap: no mention of behavior for non-existent order IDs.

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 has 100% coverage with descriptions. Description reinforces but does not add new meaning beyond examples and the all-cancel behavior. Baseline score of 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?

Clear verb 'cancel' and resource 'pending orders' with stated purpose 'manage exposure or adjust strategy'. Distinguishes well from sibling tools like create_order or open_orders.

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?

Explicitly lists when to use (remove stale orders, reduce exposure, etc.) and provides example use cases. Does not explicitly state when not to use or compare to alternatives, but 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