Skip to main content
Glama
Rift Finance MCP Server

Rift Finance MCP Server

Official
by Rift-FI

rift_bridge_execute

Initiates cross-chain bridge transfers by returning an approval link for passkey confirmation; real funds move only after approval and tokens arrive in 1–5 minutes.

Instructions

Execute cross-chain bridge. MOVES REAL FUNDS — confirm with user. Does NOT execute directly: returns an APPROVAL REQUIRED link the user approves with their passkey (check with rift_get_approval; never call again to retry). Tokens arrive 1-5 minutes after approval. Call rift_bridge_quote first to show fees. Requires login.

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_execute"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYesUSDC or USDT
amountYesAmount to bridge
recipientNoDestination address (defaults to user's wallet on dest chain)
sourceChainYesSource chain
destinationChainYesDestination chain

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.0.0

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full burden and does it well: it discloses that real funds move, that the call does not execute directly but returns an approval link requiring a user passkey, the 1-5 minute settlement window, and the anti-retry rule. These are exactly the behaviors an agent could not infer from the schema.

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?

Every sentence earns its place: the funds warning is front-loaded, the non-obvious return behavior follows immediately, and timing and prerequisites come last. No filler or repetition.

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?

For a fund-moving mutation tool with no annotations and no output schema, the description covers what the call returns (an approval link), what the user must do, how long settlement takes, and the correct follow-up tool. Nothing an agent needs to invoke it safely is missing.

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 schema already documents token, amount, recipient defaulting, and both chains. The description adds no parameter-level detail such as amount formatting, supported chain names, or whether recipient can be an off-chain identifier, so the baseline 3 applies.

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?

"Execute cross-chain bridge" gives a specific verb plus resource, and the following sentences make clear it is the execution step rather than the quote or approval-check step. An agent can distinguish it from rift_bridge_quote and rift_get_approval without 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit sequencing: call rift_bridge_quote first to show fees, confirm with the user before calling, then use rift_get_approval to check status, and never re-call to retry. Prerequisites (login) and exclusions (do not retry) are both stated.

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