Skip to main content
Glama
Rift Finance MCP Server

Rift Finance MCP Server

Official
by Rift-FI

rift_get_payment_methods

Retrieve supported banks and mobile money providers for a currency to get bank codes needed for offramping. Requires login.

Instructions

Get supported banks and mobile money providers for a currency. Use the bankCode values from here in rift_offramp. E.g. for Kenya: MPESA for M-Pesa. 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": {
      "currency": "<currency>"
    },
    "name": "rift_get_payment_methods"
  }
}

Input Schema

NameRequiredDescriptionDefault
currencyYesCurrency code: KES, NGN, UGX, GHS, ETB, CDF, TZS, MWK, BRL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.0.0

TDQS

A4.4/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden, and it discloses the key operational constraint ('Requires login') plus the read-only nature implied by 'Get' and the fact that the payload is a provider catalog keyed by currency. It does not describe the response shape (e.g. whether each entry carries a code and display name) or behavior for an unsupported currency code, which is the remaining gap.

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 plus a one-line example, front-loaded with the core purpose and followed by the downstream consumer and auth requirement. No filler and nothing repeated from the schema.

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 one parameter, no output schema, and no annotations, the definition covers purpose, auth requirement, and downstream use, which is close to everything an agent needs. The only omission is an explicit statement of what the return value looks like beyond the bankCode field.

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% and the single currency parameter is already documented with its accepted codes, so the baseline would be 3. The description adds a little beyond the schema by linking a concrete currency to a concrete returned code (Kenya → MPESA), which clarifies what the parameter actually selects.

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?

States a specific verb and resource ('Get supported banks and mobile money providers') scoped to a currency, which is plainly distinct from sibling reads like rift_get_recovery_methods, rift_get_chains, or rift_get_tokens. The example ('MPESA for M-Pesa') grounds the abstract purpose in a concrete catalog entry.

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?

Explicitly tells the agent how the output is consumed: bankCode values returned here feed rift_offramp, which effectively defines the when-to-use context (as a prerequisite lookup before an offramp call). It stops short of stating when NOT to use it or naming any alternative lookup for other regions, so it falls just under the full when/when-not bar.

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