Liquid Agent

Bridge quote (Base to 16 chains, Arc to Base)

bridge_quote

Read-onlyIdempotent

Free. Exact price to move USDC with the Liquid Bridge (Base to Arc, Arbitrum, OP, Polygon, Avalanche, Unichain, Linea, World Chain, Sonic, Monad, Sei, Ink, HyperEVM, XDC, Plume, Codex; or Arc to Base): what you pay, what you receive (exactly amount), the fee breakdown and the ETA. No payment, no wallet needed.

Input Schema

TableJSON Schema

Name	Required	Description
`to`	Yes	Chain you receive on: arc, arbitrum, optimism, polygon, avalanche, unichain, linea, world, sonic, monad, sei, ink, hyperevm, xdc, plume, codex (from Base) or base (from Arc).
`ref`	No	Optional referrer address: earns 20% of Liquid's fee. Omit if you have none.
`from`	No	Chain you pay on. Omit to pick the live route to `to` (Base to any listed chain; Arc to Base).
`amount`	Yes	USDC to RECEIVE on the destination, e.g. "1" or "25.5". Minimum 1.

Output Schema

TableJSON Schema

Name	Required	Description
`to`	No	Chain you receive on
`pay`	No	USDC you pay, all fees included
`from`	No	Chain you pay on
`note`	No	Notes
`payTo`	No	Bridge contract that receives the x402 payment
`network`	No	x402 network of the payment (CAIP-2)
`receive`	No	USDC you receive, exactly the requested amount
`allInPct`	No	Total cost as a percentage
`allInCost`	No	Total cost in USDC
`breakdown`	No	Fee breakdown: Circle network fee, Liquid fee, gas
`recipient`	No	Who receives: the payer's own address
`etaSeconds`	No	Typical delivery time

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 29, 2026

changedInput schema / properties / from / description

Previous value: -"Chain you pay on. Omit to pick the live route to `to` (base -> arc, arc -> base)."New value: +"Chain you pay on. Omit to pick the live route to `to` (Base to any listed chain; Arc to Base)."

changedInput schema / properties / to / description

Previous value: -"Chain you receive on."New value: +"Chain you receive on: arc, arbitrum, optimism, polygon, avalanche, unichain, linea, world, sonic, monad, sei, ink, hyperevm, xdc, plume, codex (from Base) or base (from Arc)."

changedInput schema / properties / to / enum

Previous value: -[
-  "arc",
-  "base"
-]New value: +[
+  "base",
+  "arc",
+  "optimism",
+  "unichain",
+  "sonic",
+  "world",
+  "monad",
+  "sei",
+  "xdc",
+  "ink",
+  "plume",
+  "polygon",
+  "avalanche",
+  "arbitrum",
+  "codex",
+  "hyperevm",
+  "linea"
+]

First observedSep 29, 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, so the description's job is lighter; it adds the cost profile (free), the prerequisite (no wallet/payment needed), and enumerates the returned fields (pay, receive, fee breakdown, ETA). No pagination or rate-limit detail, but for a read-only quote that is acceptable.

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 'Free' and the core promise, then the route list and output fields. The 16-chain parenthetical largely duplicates the schema enum, which is the one mildly wasteful element, but the rest is tight.

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?

With an output schema present and annotations covering the safety profile, the description supplies the remaining essentials: purpose, cost, no-wallet prerequisite, and route topology. Only minor gaps (minimum amount handling, error cases) remain.

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 coverage is 100%, so the schema already documents every parameter including the enums and the referrer semantics. The description only echoes that `amount` is received exactly and lists the route chains, adding marginal meaning beyond the schema's own field descriptions — baseline 3 is appropriate.

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 (moving USDC via the Liquid Bridge) and scopes it precisely to the Base->16 chains / Arc->Base routes. The word 'quote' plus 'Free' makes it distinguishable from the execution siblings like bridge_prepare_payment without opening their schemas.

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?

Makes clear this is a preview-only operation with no cost, payment, or wallet ('No payment, no wallet needed'), which tells the agent when it is safe to call. It never explicitly routes to bridge_prepare_payment for the actual transfer, so the when/when-not pairing with the sibling is left implicit.

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

All Liquid Agent 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.