Skip to main content
Glama
Rift Finance MCP Server

Rift Finance MCP Server

Official
by Rift-FI

rift_guide

Get step-by-step instructions for Rift tasks such as sending crypto, withdrawing to M-Pesa, bridging, checking balances, login, passkeys, KYC, and invoices. Use it first when exact flow is unclear.

Instructions

START HERE. Get step-by-step instructions for any Rift operation. Call this FIRST when a user asks to do something and you're not sure of the exact flow. Covers: send crypto, withdraw to M-Pesa, buy crypto, bridge, check balance, login, passkey setup and recovery, approvals, KYC, invoices, WalletConnect, auto-swap, and more.

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": {
      "task": "<task>"
    },
    "name": "rift_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskYesWhat the user wants to do, e.g. 'send USDC', 'withdraw to M-Pesa', 'check balance', 'bridge tokens', 'create invoice', 'sign up'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.0.0

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden, and it does convey that this returns instructions rather than performing the operation — a critical distinction given many siblings are mutating actions. It stops short of explicitly saying it has no side effects or what happens when the task is unsupported, which would have closed the gap fully.

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?

'START HERE' is front-loaded as the first two words, the routing rule follows immediately, and the coverage list is compact and skimmable. Every sentence adds selection value with no filler.

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, no-annotation, no-output-schema tool the description supplies purpose, timing, and scope, which is close to complete. It leaves unstated the return shape beyond 'step-by-step instructions' and how to recover if the task is not covered, a minor gap for a guidance tool.

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, and the description earns above that by enumerating the supported operation domains (send crypto, withdraw to M-Pesa, bridge, KYC, invoices, WalletConnect, auto-swap) which tells the agent what values of 'task' are meaningful. It does not specify phrasing or behavior for out-of-scope tasks, keeping it from a 5.

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 states a specific verb and resource — 'Get step-by-step instructions for any Rift operation' — and implicitly positions itself apart from the execution siblings by being the instruction-lookup tool. The coverage list makes the scope concrete rather than abstract.

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?

It gives an explicit trigger ('Call this FIRST when a user asks to do something and you're not sure of the exact flow') plus a dispute-resolution rule for the common case of ambiguous intent. That is a clear when-to-use condition with no ambiguity left for the agent.

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