Skip to main content
Glama
Sign In
edgex-mcp

edgex-mcp

by realnaka
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

edgex_cancel_order

Cancel one or more open orders by their unique order IDs. Use this tool to void pending trades and free up margin instantly.

Instructions

Cancel one or more orders by ID.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "orderIds": "<orderIds>"
    },
    "name": "edgex_cancel_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
orderIdsYesArray of order IDs to cancel

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.8

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It only says 'Cancel...' without mentioning side effects (e.g., irreversibility), whether only open orders can be cancelled, behavior on invalid IDs, or any response format. This is insufficient for a mutation tool.

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, front-loaded sentence with no redundant words. It states exactly what the tool does without any fluff, earning full marks for conciseness.

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

Completeness3/5

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

The tool has a simple one-parameter schema with complete coverage, but no output schema and no annotations. The description clearly explains the core functionality, yet leaves out information about return values, error handling, or edge cases. For a simple cancellation operation, this is minimally viable but not fully complete.

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 already provides a complete description for the single parameter (orderIds: 'Array of order IDs to cancel'), achieving 100% schema coverage. The tool description adds no additional meaning, such as ID format or semantics beyond what the schema already states, so the 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 action ('Cancel'), the resource ('orders'), and the scope ('one or more... by ID'). This distinguishes it from sibling tools like edgex_cancel_all_orders, which cancels all orders instead of specific ones.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'by ID' implies that this tool should be used when you have specific order IDs to cancel, but it does not explicitly mention alternatives or exclusions. No comparative guidance is given despite the presence of edgex_cancel_all_orders as a clear alternative.

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

Deploy Server

Other Tools