Skip to main content
Glama

Ellimist

Large-order route splitting

quantum_routing_split_order
Read-only

For large conversions: probes route output at several sizes and splits the order across routes to maximize total output versus a single route. Price: $0.05 USDC per call via x402 (no account). Not charged if it fails.

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": {
      "from_chain": "<from_chain>",
      "to_chain": "<to_chain>",
      "from_token": "<from_token>",
      "to_token": "<to_token>",
      "from_amount": "<from_amount>",
      "from_address": "<from_address>"
    },
    "name": "quantum_routing_split_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
orderNoCHEAPEST
chunksNo
backendNoclassical
slippageNo
to_chainYes
to_tokenYessymbol (ETH) or token address
from_chainYes
from_tokenYessymbol (USDC) or token address
to_addressNo
from_amountYesamount in the token's smallest unit
from_addressYes
allow_high_impactNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Adds genuinely useful context beyond the annotations: the $0.05 USDC x402 charge, no account requirement, and the no-charge-on-failure guarantee. What it leaves unresolved is whether the split is actually executed or only planned/returned, which matters because annotations declare readOnlyHint=true while 'splits the order across routes' reads like execution — the description should disambiguate this rather than rely on the agent inferring read-only.

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?

Three tight sentences with the purpose front-loaded and pricing compactly parenthesized; no filler. The one structural weakness is that the cost/payment sentence takes space that could have gone to the parameters an agent must actually set.

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

Completeness2/5

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

For a 12-parameter routing tool with no output schema and an unresolved execute-vs-quote question, the description is thin. It covers cost and failure semantics but omits what the call returns and how the splitting knobs (chunks, order, slippage, backend, allow_high_impact) affect the result.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 25% across 12 parameters, so the description carries real burden and does not meet it. Nothing explains 'chunks', 'backend' (classical vs aer), 'order', 'slippage', or 'allow_high_impact'; 'probes at several sizes' is the only faint gesture toward chunking and never names the parameter.

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?

States a specific action (splits an order across routes by probing output at several sizes) and a clear scope gate ('For large conversions'), which lets an agent tell it apart from single-route quoting or swap-building tools. It stops short of naming the sibling it supersedes, so differentiation is implied rather than explicit.

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?

'For large conversions' is an implied when-to-use condition, and 'versus a single route' hints at the alternative. However, it never states a threshold, never names which sibling to use for small conversions or for actual execution, and gives no prerequisites beyond payment.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources