Skip to main content
Glama
Rift Finance MCP Server

Rift Finance MCP Server

Official
by Rift-FI

rift_get_withdrawal_fee

Returns the raw KES buy/sell spread for internal Rift diagnostics only; for actual withdrawal fees, use the offramp rate preview instead.

Instructions

DO NOT USE THIS to show users their withdrawal fee — it only returns the raw KES buy/sell spread, not the actual fee on a withdrawal. Instead, use rift_preview_exchange_rate with an amount and type='offramp' — that returns feeBreakdown with the real fee, feePercentage, userReceivesFiat, and totalUsdcNeeded. This tool exists only for internal diagnostics.

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_withdrawal_fee"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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 burden and discloses the key behavioral trait: the returned values are not the user-facing fee, only a raw spread. It also reveals the richer return fields of the recommended alternative (feeBreakdown, feePercentage, userReceivesFiat, totalUsdcNeeded). It does not state auth requirements or the exact field names/shape of this tool's own output, which keeps it short of a 5.

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?

The warning is front-loaded in capitals, followed by the reason, the redirect with concrete arguments, and the internal-only caveat. Every sentence performs a distinct function 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 0-param, no-output-schema, no-annotation tool, the description is nearly complete: it says what comes back and steers callers away. The only gap is that the exact shape of the 'raw KES buy/sell spread' response is not described.

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 there is nothing for the description to disambiguate; the empty schema is self-explanatory. Baseline for a 0-param tool applies.

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 what the tool actually returns (the raw KES buy/sell spread) and immediately contrasts it with the sibling that returns the real withdrawal fee. An agent can distinguish this from rift_get_transaction_fee and rift_preview_exchange_rate without opening any schema.

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 when-not ('DO NOT USE THIS to show users their withdrawal fee') plus the exact alternative and arguments to use instead (rift_preview_exchange_rate with an amount and type='offramp'). The only permitted use case, internal diagnostics, is also named.

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