Skip to main content
Glama
Rift Finance MCP Server

Rift Finance MCP Server

Official
by Rift-FI

rift_preview_exchange_rate

Preview offramp or onramp exchange rates and fee breakdowns to see fiat received or USDC needed before converting.

Instructions

Preview exchange rate. IMPORTANT: offramp and onramp rates are DIFFERENT — always set type correctly.

Rate fields explained:

  • buying_rate = OFFRAMP/withdrawal rate — fiat per USDC when cashing out. Multiply USDC × buying_rate to get fiat the user receives.

  • selling_rate = ONRAMP/deposit rate — fiat per USDC when buying crypto. User pays this much fiat per USDC.

To show a user's balance in local fiat: USDC balance × buying_rate. To show how much USDC they get for fiat: fiat amount / selling_rate.

Pass an amount to get feeBreakdown with exact fee, feePercentage, userReceivesFiat, and totalUsdcNeeded.

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": {
      "currency": "<currency>",
      "type": "<type>"
    },
    "name": "rift_preview_exchange_rate"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeYesMUST match operation: 'offramp' = selling crypto, 'onramp' = buying crypto
amountNoAmount in USDC to preview
currencyYesFiat currency: KES, NGN, UGX, GHS, ETB, CDF, TZS, MWK, BRL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.0.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It discloses the conditional behavior of amount (returns feeBreakdown with exact fee, feePercentage, userReceivesFiat, totalUsdcNeeded) and the rate-field semantics, but never states that it is read-only/non-mutating, whether authentication is needed, or anything about rate limits or freshness of the quote.

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-loads the critical warning about type, then uses a compact labeled list for rate fields. Slightly redundant, since the 'USDC balance × buying_rate' and 'fiat / selling_rate' formulas restate the field definitions already given, but the repetition aids comprehension rather than wasting much space.

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 no output schema, the description correctly takes on the job of explaining return values (buying_rate, selling_rate, feeBreakdown fields) and how to interpret them. The remaining gap is the absence of any statement about the operation's side-effect-free nature or any preconditions, which matters given zero annotation coverage.

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

Parameters4/5

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

Schema coverage is 100% so the baseline is 3, but the description adds real meaning beyond the schema by explaining the consequence of passing amount (feeBreakdown contents) and reinforcing the offramp/onramp distinction with directional semantics for buying_rate and selling_rate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource (preview exchange rate) and immediately clarifies the two operating modes, offramp vs onramp, which an agent must get right. It does not name any sibling (e.g. rift_bridge_quote or rift_get_transaction_fee) to differentiate itself, so it falls short of a 5.

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?

Gives concrete usage context: use buying_rate to display a balance in local fiat, use selling_rate to convert fiat into USDC, and pass amount to obtain a feeBreakdown. It warns emphatically to set type correctly. No when-not-to-use guidance or alternative tool is offered, so it is clear context but not full routing guidance.

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