Armor Crypto MCP

Official

by armorwallet

Overview Schema Source Related Servers Discussions Admin

Python

Remote

cancel_order

Cancel a limit, take profit, or stop loss order by providing the order ID.

Instructions

Cancel a limit, take profit or stop loss order.

Expects a CancelOrderRequestContainer, returns a CancelOrderResponseContainer.

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": {
      "cancel_order_requests": "<cancel_order_requests>"
    },
    "name": "cancel_order"
  }
}

Input Schema

Name	Required	Description	Default
`cancel_order_requests`	Yes

Output Schema

Name	Required	Description	Default
`cancel_order_responses`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 18, 2025

TDQS

B3.2/5.0

Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It mentions the expected request and response types but does not note side effects, required permissions, or idempotency, which are important for a cancellation action.

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 two concise sentences, front-loading the purpose. It could be slightly longer to include usage hints, but it is not verbose.

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?

For a simple tool with one parameter and an output schema, the description covers the essential purpose and input/output format. However, it omits error scenarios and idempotency, leaving some completeness gaps.

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 0% for the top-level parameter, but the description adds that it expects a CancelOrderRequestContainer. This provides context beyond the schema, though it does not detail the structure of inner fields.

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') and the resource ('a limit, take profit or stop loss order'), using a specific verb and resource. This distinguishes it from sibling tools like 'create_order' or 'get_all_orders'.

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?

The description does not provide guidance on when to use this tool versus alternatives like 'cancel_dca_order'. It simply states what it cancels, leaving the agent to infer usage context.

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