Kellian

Cancel an order authoritatively at the hosted layer, by hash or client order id

kellian_cancel_order

Destructive

Cancel an order authoritatively by order hash or client order id. Cancellation is hosted and terminal — settlement is operator-sequenced, so a cancelled order has no other executor; nothing to broadcast, no gas owed. An order with a committed taker reservation is suspended and terminalizes when that fill settles or releases.

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": {
      "walletAddress": "<walletAddress>",
      "walletSignature": "<walletSignature>",
      "signatureTimestamp": "<signatureTimestamp>",
      "proofNonce": "<proofNonce>",
      "idempotencyKey": "<idempotencyKey>"
    },
    "name": "kellian_cancel_order"
  }
}

Input Schema

Name	Required	Description
`clOrdId`	No	Client order id to cancel (resolves to the live open/partially-filled order for this wallet with this clOrdId). Provide this OR orderHash.
`orderHash`	No	Order hash to cancel
`proofNonce`	Yes	Required single-use nonce for the wallet proof. Fetch from POST /api/auth/nonce; consumed on verification so the proof cannot be replayed.
`walletAddress`	Yes	Wallet address that owns the order
`idempotencyKey`	Yes	Stable retry key. Reuse only with byte-equivalent tool arguments.
`walletSignature`	Yes	Action-bound wallet proof. Sign the canonical 'problee-mcp-auth:…' challenge (binds agent, apiKey, tool, scope, chain, resource, payloadHash, nonce, timestamp).
`signatureTimestamp`	Yes	Unix timestamp (seconds) used in the signed challenge message

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 5, 2026

TDQS

A3.5/5.0

Behavior4/5

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

Beyond the destructive and non-idempotent annotations, the description discloses important behavior: cancellation is hosted and terminal, requires no broadcast or gas, and a committed taker reservation causes suspension until settlement or release. It does not address error cases or auth requirements, but those are largely covered by the schema.

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 three tightly written sentences, front-loaded with the action and then the behavioral implications. It earns most of its length, though the final sentence is dense and could be slightly clearer.

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 that an output schema exists and parameter semantics are fully documented in the schema, the description covers the key behavioral context an agent needs to invoke cancellation correctly. The main missing piece is explicit differentiation from sibling cancellation tools.

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 both orderHash and clOrdId are already documented, including that one or the other must be provided. The description's 'by order hash or client order id' adds a useful summary but no meaning beyond the schema.

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 states a specific verb and resource: cancel an order by order hash or client order id. It is clear what the tool does, but it does not distinguish itself from sibling cancel tools such as kellian_cancel_orders, kellian_cancel_all_orders, or kellian_confirm_order_cancel.

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 explains the semantics of cancellation but gives no explicit when-to-use guidance relative to alternatives. With several sibling cancellation tools available, an agent is left to infer whether this is for single orders, batch orders, or confirmation flows.

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

All Kellian tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?