Trnch on Elysium

Quote a swap

trnch_quote

Read-onlyIdempotent

Quote any pair on Elysium across three routers (Uniswap, KyberSwap and LI.FI) without building a transaction. Returns the best amount out, already net of the Trnch fee, the router and the fee rate in basis points (feeBps). Native HYPE is the zero address. No API key needed for a quote; a transaction (trnch_buy, trnch_sell) needs one.

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": {
      "tokenIn": "<tokenIn>",
      "tokenOut": "<tokenOut>",
      "amountIn": "<amountIn>"
    },
    "name": "trnch_quote"
  }
}

Input Schema

Name	Required	Description
`fast`	No	Return the first clean quote after about 250 ms instead of waiting for the best price. Default false.
`tokenIn`	Yes	Token sold: a Elysium token address, or the zero address for HYPE.
`amountIn`	Yes	Amount of tokenIn in its smallest unit (wei-style integer string).
`slippage`	No	Max slippage as a fraction (0.01 = 1%). Default 0.01.
`tokenOut`	Yes	Token bought: a Elysium token address, or the zero address for HYPE.
`decimalsIn`	No	Decimals of tokenIn. Default 18: set it for USDC (6) and other non-18 tokens.
`decimalsOut`	No	Decimals of tokenOut. Default 18: set it for USDC (6) and other non-18 tokens.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds real value beyond that: which routers are aggregated, that the returned amount is already net of the Trnch fee, that feeBps is returned, and that no API key is required. Failure modes and rate limits are not mentioned.

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?

Four short sentences, front-loaded with the core purpose, followed by return shape, the HYPE address convention, and the auth distinction. The HYPE sentence duplicates the schema and is the one line that does not fully earn its place.

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?

No output schema exists, and the description compensates by naming the return fields (best amount out net of fee, router, feeBps). Combined with the fully documented input schema and read-only annotations, an agent has enough to call it correctly; only latency/error behavior is left implicit.

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 all seven parameters are already documented, including the zero-address convention for HYPE and the decimals defaults. The description's only parameter-adjacent note ('Native HYPE is the zero address') restates what the schema already says, adding no new meaning. 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 (quote) and resource (any pair on Elysium across Uniswap, KyberSwap, LI.FI), and explicitly contrasts with transaction-building siblings trnch_buy and trnch_sell. An agent can distinguish this from the swap-execution tools without opening either 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?

Gives clear context for use ('without building a transaction', 'no API key needed for a quote') and names the alternatives that require a key (trnch_buy, trnch_sell). It stops short of an explicit 'call this before executing a swap to preview the price' instruction, but the routing is unambiguous.

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

All Trnch on Elysium 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?