TRDEFI Liquidity

Fusion quote (gasless, gated liquidity)

trdefi_fusion_quote

Read-onlyIdempotent

A 1inch Fusion quote for a token pair. Use this when a position answers "Strategy is gated": the user/agent does not need an Aqua NFT, because a 1inch resolver with the credential fills the order. Returns the expected output, the Fusion resolver fee and a quote id. Free, read-only, nothing signed or moved. Chain, token addresses and base-unit amounts come from trdefi_positions / trdefi_chains. Note: a Fusion fill is best-effort, not guaranteed: the resolver chooses the venue, and a gated Aqua position is used only if that resolver holds the Aqua NFT.

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": {
      "chain": "<chain>",
      "fromToken": "<fromToken>",
      "toToken": "<toToken>",
      "amount": "<amount>",
      "wallet": "<wallet>"
    },
    "name": "trdefi_fusion_quote"
  }
}

Input Schema

Name	Required	Description
`chain`	Yes	Network key, e.g. "ethereum", "base", "arc".
`amount`	Yes	Input amount in token base units, as an integer string.
`preset`	No	Auction preset. Defaults to the quote recommendation.
`wallet`	Yes	The address that will sign the Fusion order.
`toToken`	Yes	Output token address.
`fromToken`	Yes	Input token address.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations declare readOnly/idempotent/non-destructive, and the description goes well beyond them: 'Free, read-only, nothing signed or moved', the exact return contents (expected output, resolver fee, quote id), and a critical caveat that a Fusion fill is best-effort, not guaranteed, since the resolver chooses the venue. That best-effort warning is exactly the kind of behavioral caveat annotations cannot carry.

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 one-line purpose, then the gating condition, then return values, then the caveat — a sensible ordering with no filler. It is on the long side for a quote tool, but each sentence (especially the resolver-venue caveat) carries real decision weight.

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?

There is no output schema, so the description must describe the return values, and it does (expected output, resolver fee, quote id). Combined with the gating prerequisite, the safety statement and the best-effort caveat, an agent has everything needed to call it and to interpret the caveat correctly.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description earns extra by telling the agent where values come from — 'Chain, token addresses and base-unit amounts come from trdefi_positions / trdefi_chains' — which resolves the base-unit-vs-decimal ambiguity indirectly. It does not discuss the 'preset' enum or the wallet signing role further, keeping it below a 5.

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+resource ('A 1inch Fusion quote for a token pair') and immediately scopes it to the gated-strategy case where no Aqua NFT is required. That framing distinguishes it from the sibling trdefi_quote (ungated) and trdefi_fusion_prepare/submit without the agent opening any 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 an explicit selection rule: 'Use this when a position answers "Strategy is gated"', and explains why (a 1inch resolver with the credential fills the order, no Aqua NFT needed). It stops short of naming trdefi_quote as the non-gated alternative by name, so routing back to the sibling is left slightly implicit.

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

All TRDEFI Liquidity 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?