Kellian

Cancel a named set of orders in one call, reporting each hash independently

kellian_cancel_orders

Destructive

Cancel up to 50 named orders in one call. Sits between cancelling one hash and cancelling everything: a maker re-quoting part of a ladder wants neither six round trips nor a teardown of the book it is about to rebuild. Every hash is reported on its own — unknown, already terminal, or not yours does not stop the rest — because cancellation reduces risk, and a batch that refused wholesale would leave exposure the caller explicitly asked to drop. Hosted and terminal: nothing to broadcast, no gas owed.

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

Input Schema

Name	Required	Description
`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.
`orderHashes`	Yes	Order hashes to cancel, up to 50. Duplicates are collapsed.
`walletAddress`	Yes	Wallet address that owns the orders
`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

A4.4/5.0

Behavior5/5

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

Annotations only say destructive/open-world/non-idempotent; the description adds the operationally critical fact that the batch is non-atomic — unknown, terminal, or unauthorized hashes are reported individually and do not abort the rest — plus that it is hosted and terminal with nothing to broadcast and no gas owed. That is exactly the failure-mode and settlement information an agent cannot get from the hints.

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?

Front-loaded with the action and cap, then rationale, then failure semantics, then settlement cost — a sensible order with no filler sentences. The ladder-re-quoting imagery is slightly ornate for a tool description, but it does carry the routing signal.

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

Completeness5/5

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

With an output schema present, per-hash result reporting need not be spelled out, and authentication details live in the schema. What remains — scope, atomicity, cost, and placement among the cancel siblings — is fully covered for a destructive six-parameter mutation.

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 coverage is 100%, and every parameter (orderHashes, walletAddress, walletSignature, signatureTimestamp, proofNonce, idempotencyKey) already carries its own description. The description only restates the 50-item cap, adding no syntax or constraint beyond the schema, so the baseline 3 applies.

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?

"Cancel up to 50 named orders in one call" gives a specific verb, resource, and batch bound, and the ranking sentence ("sits between cancelling one hash and cancelling everything") positions it against the cancel_order and cancel_all_orders siblings. An agent can distinguish all three without opening a schema.

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?

The re-quoting-a-ladder scenario makes the intended use concrete and implicitly excludes both the single-hash and full-teardown paths by describing what the caller doesn't want. It never names the sibling tools explicitly nor states a hard when-not case, so routing relies on the reader mapping "one hash" / "everything" to the actual tool names.

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?