Skip to main content
Glama
Rift Finance MCP Server

Rift Finance MCP Server

Official
by Rift-FI

rift_get_transaction_fee

Calculates the on-chain gas/network fee for sending crypto, helping you estimate transaction costs before initiating a transfer.

Instructions

Calculate the gas/network fee for sending crypto (rift_send_crypto). This is the on-chain transaction fee, NOT the offramp/exchange fee. For offramp fees, use rift_preview_exchange_rate with amount and type='offramp'. 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": {
      "recipient": "<recipient>",
      "amount": "<amount>",
      "chain": "<chain>",
      "token": "<token>"
    },
    "name": "rift_get_transaction_fee"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainYesChain
tokenYesToken
amountYesAmount to send
recipientYesRecipient address

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?

No annotations are supplied, so the description carries the burden: it discloses that this is a read-only calculation rather than an actual send, and that authentication is required. It does not cover whether the quote is cached/time-sensitive or what happens if the recipient is invalid, so it falls short of full behavioral disclosure.

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, front-loaded with the primary purpose, followed by the disambiguation and the auth requirement. Every sentence contributes and no wording is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, no annotations, and four required parameters, the description should say something about what the fee result looks like (native token vs. fiat, single value vs. breakdown). It nails routing and prerequisites but leaves the return value entirely unexplained.

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%, so recipient, amount, chain, and token are all documented in the schema; the description adds no syntax, format, or dependency detail (e.g., whether token must belong to chain). Baseline 3 is appropriate where the schema does the heavy lifting.

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 ('Calculate the gas/network fee for sending crypto') and explicitly scopes it as the on-chain transaction fee, not an offramp/exchange fee. An agent can distinguish it from rift_preview_exchange_rate and rift_get_withdrawal_fee without opening either 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?

Explicitly ties the tool to rift_send_crypto and routes offramp-fee questions to rift_preview_exchange_rate with a concrete argument hint (amount, type='offramp'). It also states the 'Requires login' precondition, so both the selection condition and the access requirement are covered.

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