Skip to main content
Glama
ultrade-org

Ultrade MCP Server

Official
by ultrade-org

ultrade_market_cancel_orders

Cancel multiple open trading orders on the Ultrade platform by specifying order IDs, wallet address, and session token.

Instructions

Cancel multiple open orders

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
orderIdsYesArray of order IDs to cancel
walletAddressYesLogin wallet address
walletTokenYesLogin session token
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states 'Cancel multiple open orders' but lacks behavioral details: no mention of permissions required, whether cancellation is reversible, rate limits, error handling, or what happens if some orders fail. For a mutation tool with zero annotation coverage, this 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 waste. It's front-loaded and appropriately sized for its purpose, making it easy to parse quickly.

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 this is a mutation tool with no annotations and no output schema, the description is incomplete. It doesn't cover behavioral aspects like side effects, authentication needs (implied by wallet parameters but not stated), or response format, leaving critical gaps for agent invocation.

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 parameters are fully documented in the schema. The description adds no additional meaning beyond implying 'orderIds' refers to 'multiple open orders', which is already clear from the schema. Baseline 3 is appropriate as the schema does the heavy lifting.

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 'Cancel multiple open orders' clearly states the verb ('Cancel') and resource ('multiple open orders'), making the purpose unambiguous. However, it doesn't differentiate from sibling 'ultrade_market_cancel_order' (singular), which might be important for agent selection.

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?

No guidance on when to use this tool versus alternatives like 'ultrade_market_cancel_order' (singular) or prerequisites. The description implies it's for multiple orders but doesn't specify thresholds or constraints, leaving usage context unclear.

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/ultrade-org/ultrade-mcp'

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