aeX402 — Cross-Chain DeFi MCP: LINQ, AMM, Bridge, AI

bridge_quote

Bridge/swap ANY asset across ANY chain via LI.FI (the engine behind Jumper) — e.g. Arbitrum USDC → Robinhood Chain (4663) USDG, or bridge into ETH for gas. Returns the best route (estimated output, fees, bridge used, duration) PLUS an unsigned transactionRequest (to/data/value/gasLimit) that the CALLER signs and submits on the fromChain — no keys are held here. Chains by id or key (1 Ethereum, 42161 Arbitrum, 8453 Base, 10 Optimism, 137 Polygon, 999 HyperEVM, 4663 Robinhood Chain). Tokens by symbol or 0x address.

Input Schema

TableJSON Schema

Name	Required	Description
`toChain`	Yes	Destination chain id or key, e.g. 4663 (Robinhood Chain)
`toToken`	Yes	Destination token symbol or 0x address, e.g. USDG or ETH
`fromChain`	Yes	Source chain id or key, e.g. 42161 or ARB
`fromToken`	Yes	Source token symbol or 0x address, e.g. USDC
`toAddress`	No	Recipient on the destination chain (defaults to fromAddress)
`fromAmount`	Yes	Amount in the source token's smallest unit (e.g. 1000000 = 1 USDC at 6 decimals)
`fromAddress`	Yes	Sender 0x address on the source chain

Output Schema

TableJSON Schema

Name	Required	Description
`note`	No
`bridge`	Yes	bridge tool used (e.g. across)
`toToken`	No
`toAmount`	Yes
`fromToken`	No
`toAddress`	No
`toChainId`	No
`feeCostUsd`	No
`fromAmount`	No
`gasCostUsd`	No
`fromAddress`	No
`fromChainId`	No
`toAmountMin`	No
`toTokenAddress`	No
`fromTokenAddress`	No
`transactionRequest`	Yes	UNSIGNED tx (to, data, value, gasLimit) — caller signs & submits on the fromChain
`estimatedDurationSec`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedAug 2, 2026
- addedOutput schema / properties / fromAddress
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / fromChainId
```
Added value: +{
+  "type": "integer"
+}
```
- addedOutput schema / properties / fromTokenAddress
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / toAddress
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / toChainId
```
Added value: +{
+  "type": "integer"
+}
```
- addedOutput schema / properties / toTokenAddress
```
Added value: +{
+  "type": "string"
+}
```
First observedJul 17, 2026

TDQS

A4.8/5.0

Behavior5/5

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

The description discloses that the tool returns an unsigned transactionRequest for the caller to sign and submit, and that no keys are held. It also explains what the return includes (estimated output, fees, bridge used, duration). This is transparent about not executing transactions, which is critical for an agent.

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?

The description is a single dense paragraph but is well-structured: core purpose first, then example, then return details, then accepted inputs. Every sentence adds information without redundancy.

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?

Given that an output schema exists and is not provided here, the description sufficiently covers the tool's purpose, input format, and behavioral output. It addresses the parameters indirectly and explains the transaction workflow, making it complete for an agent to select and invoke the tool.

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

Parameters5/5

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

The description supplements the already-complete schema with helpful examples: amount in smallest unit (e.g., 1000000 = 1 USDC at 6 decimals), chain ids/keys, and token symbols/addresses. This adds significant value beyond the schema.

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 description clearly states the tool's function: it bridges/swaps any asset across any chain via LI.FI, returns the best route plus an unsigned transactionRequest. It distinguishes from sibling tools by specifying cross-chain functionality and the unsigned tx output.

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 provides context on when to use this tool (cross-chain swaps, bridging into ETH for gas) but does not explicitly mention alternatives or when-not-to-use. It implies the use case but lacks explicit exclusions.

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

All aeX402 — Cross-Chain DeFi MCP: LINQ, AMM, Bridge, AI 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?