Skip to main content
Glama
Rift Finance MCP Server

Rift Finance MCP Server

Official
by Rift-FI

rift_get_approval

Check the status of an approval request from a fund-moving action such as send, swap, bridge, or sign, and confirm whether it is pending, approved, rejected, expired, or failed.

Instructions

Check an approval request returned by a fund-moving tool (send, offramp, bridge, swap, WalletConnect approve, send transaction, sign message). Status: pending (user hasn't approved yet — remind them of the link), approved (result has transactionHash / userOpHash / signature), rejected, expired (start over with a new call), failed. Works with the API key alone.

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": {
      "approvalId": "<approvalId>"
    },
    "name": "rift_get_approval"
  }
}

Input Schema

NameRequiredDescriptionDefault
approvalIdYesapprovalId from the APPROVAL REQUIRED message

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.0.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the disclosure burden and does reasonably well: it enumerates the five possible statuses, explains what approved means in terms of returned artifacts (transactionHash / userOpHash / signature), and states the auth requirement ('works with the API key alone'). It stops short of saying the call is read-only or non-destructive in so many words, and says nothing about rate limits or whether polling is expected.

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?

The scope statement is front-loaded and the status breakdown is compact and information-dense, with each state paired with its consequence. The parenthetical list of fund-moving tools is somewhat bulky, but it earns its place by tying the tool to specific callers.

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?

For a single-parameter polling tool with no output schema, the description supplies the essential contract: where the ID comes from, what each status means, and what to do next per status. Polling cadence and the response shape beyond status fields are the remaining gaps, but nothing critical to correct invocation 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% for the single approvalId parameter, and the description adds only the origin context (returned by a fund-moving tool) which the schema already conveys via 'from the APPROVAL REQUIRED message'. Baseline 3 applies since the schema does the parameter work.

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 gives a specific verb and resource ('Check an approval request') and immediately scopes it to approvals produced by fund-moving tools (send, offramp, bridge, swap, WalletConnect approve, sign message). This clearly separates it from the many rift_get_* status/list siblings, which do not concern approval lifecycle.

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?

It tells the agent when this tool is applicable (after a fund-moving tool returns an APPROVAL REQUIRED message) and prescribes actions per state: pending means remind the user of the link, expired means start over with a new call. There is no explicit 'do not use this for X' exclusion, but the procedural guidance is unusually concrete.

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