Skip to main content
Glama
Rift Finance MCP Server

Rift Finance MCP Server

Official
by Rift-FI

rift_get_deposit_stats

Retrieve total deposit counts and USDC and KES amounts plus the full deposits list for all onchain deposits to the user's wallets. Use it to summarize deposit activity after login.

Instructions

Get deposit statistics: totalDeposits (count), totalUsdcAmount, totalKesAmount, plus the full deposits list. Summary of all onchain deposits to the user's wallets. 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_deposit_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.0.0

TDQS

A3.6/5.0
Behavior3/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 disclose one important behavioral fact: 'Requires login.' It also reveals that results are scoped to 'the user's wallets' and that both aggregates and a full list come back together. It says nothing about whether the aggregate covers all history or a window, whether the list is paginated or capped, or how large the response can be – meaningful gaps for a list-bearing read tool with zero annotation coverage.

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?

Two short sentences, front-loaded with the return payload and ending with the access prerequisite. Every clause adds information; the field enumeration is slightly dense but directly useful given there is no output 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?

No output schema exists, so the description must describe the return value – and it does, naming the three aggregates and the included deposits list. For a zero-parameter read tool this is largely sufficient; the remaining gap is the unexplained relationship to rift_get_deposits and the lack of any scope or size limits on the returned list.

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 no parameters, so there is no parameter semantics to explain and the baseline of 4 applies. Nothing in the description implies hidden inputs that the empty schema omits.

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 ('Get deposit statistics') and enumerates the exact aggregates returned (totalDeposits, totalUsdcAmount, totalKesAmount) plus the companion deposits list. This is far more specific than the title alone, though it never distinguishes itself from the sibling rift_get_deposits, which it partly duplicates by returning 'the full deposits list'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the words 'statistics' and 'Summary of all onchain deposits' suggest this is the aggregate-view tool an agent would pick when it needs totals rather than raw entries. There is no explicit when-to-use, when-not-to-use, or pointer to rift_get_deposits for the plain list, and the fact that it also returns every deposit blurs the boundary further.

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