Kellian

Place up to 50 pre-signed limit orders in one call (partial success). Counts as ONE write against the rate limiter regardless of batch size.

kellian_batch_place_orders

Place up to 50 pre-signed limit orders in one call (ONE write credit). Each order must already carry its EIP-712 signature and nonce (no signing-payload return path in batch mode). Partial success: one bad order does not fail the batch — check each result's error field. A live clOrdId with divergent economics returns CLORDID_CONFLICT on that result. Requires wallet proof.

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

Input Schema

Name	Required	Description
`orders`	Yes	Orders to place, in order. Response results are index-aligned.
`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 placing the orders
`idempotencyKey`	Yes	Required write-safety key for this batch
`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.5/5.0

Behavior5/5

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

Goes well beyond the annotations by disclosing the rate-limiter accounting (one write regardless of batch size), the partial-success contract ('one bad order does not fail the batch'), where to look for failures (each result's `error` field), and the CLORDID_CONFLICT outcome for divergent economics on a live clOrdId. These are exactly the behaviors an agent cannot infer from readOnlyHint/destructiveHint/idempotentHint.

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?

Five short sentences, each earning its place: capability, precondition, failure semantics, conflict case, auth requirement. The most decision-relevant fact (one write credit) is front-loaded in the first sentence.

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?

An output schema exists, so return shape need not be explained, yet the description still tells the agent where to detect per-order failure. Combined with the pre-signing requirement, auth proof, batch ceiling, and conflict handling, nothing an agent needs to invoke this correctly is missing.

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% and the nested order fields are exhaustively documented, so the schema carries the parameter burden. The description adds only the response-alignment contract (index-aligned results) and the error-field convention, both of which are largely restated from the schema's 'Orders to place, in order. Response results are index-aligned.' 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?

States a specific verb (place), resource (pre-signed limit orders), and scope (up to 50 in one call), which cleanly separates it from the single-order sibling kellian_place_limit_order and from kellian_batch_prepare_orders. The parenthetical 'ONE write credit' front-loads the distinguishing economic property.

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?

Establishes the prerequisite clearly: each order must already carry its EIP-712 signature and nonce, and there is 'no signing-payload return path in batch mode' — effectively routing the agent to a prepare step first. It also flags 'Requires wallet proof.' It stops short of naming the sibling tool to call for signing payloads, so the routing is implied rather than explicit.

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?