TRDEFI Liquidity

Submit a signed Fusion order

trdefi_fusion_submit

Destructive

Forward an already-signed Fusion order to 1inch's relayer. The signature is the user's authorization; this server never signs and never holds a key. Pass the order, signature, extension and quoteId returned by trdefi_fusion_prepare. A resolver fills the order later; submission does not guarantee a fill.

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>",
      "order": "<order>",
      "signature": "<signature>"
    },
    "name": "trdefi_fusion_submit"
  }
}

Input Schema

Name	Required	Description
`chain`	Yes	Network key, e.g. "ethereum", "base", "arc".
`order`	Yes	The signed Fusion order object returned by trdefi_fusion_prepare (`order`).
`quoteId`	No	The `quoteId` returned by trdefi_fusion_prepare.
`extension`	No	The `extension` returned by trdefi_fusion_prepare. Defaults to 0x.
`signature`	Yes	EIP-712 signature from the wallet (0x-prefixed hex).

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations already declare destructive, open-world, and non-idempotent behavior. The description adds important context beyond annotations: the server never signs or holds keys, the signature is the user's authorization, a resolver fills later, and submission does not guarantee a fill.

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?

Three sentences, front-loaded with purpose, followed by key safety and outcome context. Every sentence adds useful information without repetition.

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?

Given the rich annotations and complete schema, the description covers the important behavioral caveats for a submit/mutation tool. With no output schema, it leaves a small gap by not describing the response shape, such as success status or order identifier.

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 the baseline is 3. The description restates that four inputs come from trdefi_fusion_prepare, but the schema already documents that provenance, and the description omits the chain parameter entirely.

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?

The first sentence states a specific verb, resource, and destination: forward an already-signed Fusion order to 1inch's relayer. It also distinguishes this from trdefi_fusion_prepare by naming the source of the required inputs.

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 description clearly establishes the prerequisite flow: pass the order, signature, extension, and quoteId returned by trdefi_fusion_prepare. It does not explicitly state when not to use this tool or name alternative siblings, so it falls short of a full 5.

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?