Skip to main content
Glama
Rift Finance MCP Server

Rift Finance MCP Server

Official
by Rift-FI

rift_get_deposits

Retrieve onchain deposit history of inbound USDC transfers to smart wallets, including amounts, KES conversion, sender, tx hash, and timestamp. Not a balance check.

Instructions

Get onchain deposit history for the user (queried live from The Graph). Shows inbound transfers to the user's smart wallets with USDC amounts, KES conversion, sender address, tx hash, and timestamp. This is NOT a balance check — use rift_get_balance for current balances. 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_deposits"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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?

With no annotations, the description carries the full behavioral burden and does meaningful work: it discloses the live external data source (The Graph), the authentication requirement, and the semantic content of results. Remaining gaps are pagination/result-size limits and ordering, which matter for a zero-parameter list call that may return everything.

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: purpose and scope first, then returned fields, then the negative disambiguation and auth note. No filler, no restatement of the tool name, and the exclusions are placed after the agent already knows what the tool does.

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?

There is no output schema, so the description's field list (USDC amounts, KES conversion, sender, tx hash, timestamp) is load-bearing and adequately compensates. For a parameterless read tool the definition is nearly sufficient; only ordering, pagination, or empty-history behavior are unstated.

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?

The tool takes zero parameters, so the schema has nothing to explain and the baseline is 4. The description correctly avoids inventing filter arguments and instead spends its words on output semantics.

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 onchain deposit history), scopes it to inbound transfers to the user's smart wallets, and enumerates the returned fields (USDC amount, KES conversion, sender, tx hash, timestamp). It also explicitly contrasts itself with rift_get_balance, so an agent can distinguish it from the nearest sibling without opening a schema.

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 an explicit when-not ('This is NOT a balance check — use rift_get_balance for current balances') plus a prerequisite ('Requires login'). It does not address adjacent siblings such as rift_get_deposit_stats or rift_get_transaction_history, so the alternative-routing is clear but not exhaustive.

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