Skip to main content
Glama
Rift Finance MCP Server

Rift Finance MCP Server

Official
by Rift-FI

rift_get_balance

Retrieve your crypto wallet balances across all supported chains or filter by chain and token. Use it to check USDC, USDT, ETH and other holdings before sending, swapping, or offramping funds.

Instructions

Get wallet balance. Returns crypto balances (USDC, USDT, ETH, etc), NOT fiat amounts. Call with no params for all balances across all chains. To display in local fiat: call rift_preview_exchange_rate with type='offramp', then multiply USDC balance × buying_rate. Requires login.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "rift_get_balance"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNoOptional filter by chain: BASE, POLYGON, ARBITRUM, ETHEREUM, LISK, BNB, BERACHAIN, CELO. Omit for all chains
tokenNoOptional filter by token: USDC, USDT, ETH, BTC, etc. Omit for all tokens

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.0.0

TDQS

A4.3/5.0
Behavior4/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 disclose an auth prerequisite ('Requires login') plus the scope of returned data (crypto only, not fiat). It does not describe freshness/caching, whether balances are per wallet instance, or how multi-chain results are grouped, which are the remaining behavioral gaps for a zero-annotation tool.

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?

Four short sentences, front-loaded with purpose and the fiat distinction before the operational guidance; every sentence carries information. The 'Requires login' prerequisite is tacked on at the end where a caller might skim past it.

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 two-optional-param read with no annotations and no output schema, the description covers purpose, return content, auth requirement and the fiat-display workflow. The main omission is the shape of the returned balance data, though the narrow scope limits how much that matters.

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% and both params already document their chain/token value sets and the 'omit for all' default, so the baseline is 3. The description's 'call with no params for all balances across all chains' only reinforces the combined default already stated in the schema, adding little new semantics such as case sensitivity or filter interaction.

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 wallet balance') and immediately scopes the return set ('crypto balances (USDC, USDT, ETH, etc), NOT fiat amounts'). The explicit exclusion of fiat distinguishes it from rift_preview_exchange_rate and the other siblings without requiring the schema to be opened.

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?

Gives a concrete invocation rule ('Call with no params for all balances across all chains') and a named alternative path for fiat display, including the exact sibling, the required parameter value (type='offramp') and the arithmetic to apply (USDC balance × buying_rate). Nothing about when to use this vs. the exchange-rate tool is left to inference.

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