Skip to main content
Glama
Rift Finance MCP Server

Rift Finance MCP Server

Official
by Rift-FI

rift_bridge_quote

Get the fee and expected output amount for a cross-chain bridge transfer before executing it, so users can see exactly what they will receive.

Instructions

Get fee and output amount for a bridge transfer. Call before rift_bridge_execute to show user what they'll receive. No auth required.

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": {
      "sourceChain": "<sourceChain>",
      "destinationChain": "<destinationChain>",
      "token": "<token>",
      "amount": "<amount>"
    },
    "name": "rift_bridge_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYesUSDC or USDT
amountYesAmount to bridge
sourceChainYesSource chain: ARBITRUM, BASE, POLYGON, etc
destinationChainYesDestination chain

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.0.0

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description must carry behavioral weight; it does disclose "No auth required" and frames the call as a non-mutating preview, which is genuinely useful. However, it omits quote validity/expiry, whether the quote is binding, and how slippage or rate changes are handled — all material for a pre-execution quote.

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 short sentences, front-loaded with the purpose and followed by the sequencing instruction. No filler, no restatement of the tool name, and nothing that could be cut without losing information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 signal the return shape; it does name fee and output amount, which covers the essentials. But it omits quote lifetime and whether the quoted rate is guaranteed at execution time, a gap that matters for a tool whose whole job is a pre-commitment estimate.

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 four parameters are already documented in the schema, establishing a baseline of 3. The description adds no parameter-level meaning (e.g., whether token symbol must match the source chain, or supported amount ranges), so it does not exceed that baseline.

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?

"Get fee and output amount for a bridge transfer" names a specific verb and the exact data returned, and it is instantly distinguishable from rift_bridge_execute. An agent knows this is the read-only pricing step, not the transfer itself.

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?

"Call before rift_bridge_execute to show user what they'll receive" gives an explicit ordering and a named alternative, which is strong guidance. It does not address when NOT to call this (e.g., versus rift_get_bridge_routes for comparing routes), so it stops just short of full alternative coverage.

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

Deploy Server

Other Tools