Skip to main content
Glama
Rift Finance MCP Server

Rift Finance MCP Server

Official
by Rift-FI

rift_get_wallet_instance

Retrieve the wallet address and details for a specified blockchain after login, so you can check balances, send crypto, or bridge funds across supported chains.

Instructions

Get wallet address and details for a specific chain. 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": {
      "chain": "<chain>"
    },
    "name": "rift_get_wallet_instance"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainYesChain: BASE, POLYGON, ARBITRUM, ETHEREUM, etc

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.0.0

TDQS

B3.1/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full behavioral burden. It discloses the login requirement and implies a read via 'Get,' but does not clarify whether a missing wallet is created, what 'details' includes, or how errors are handled.

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 description is two short, front-loaded sentences with no wasted wording. The core purpose is stated first and the login prerequisite follows immediately.

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?

For a simple one-parameter read tool, the definition is minimally adequate. However, without an output schema it does not clarify the returned 'details,' and without annotations it leaves read-only behavior and failure modes implicit.

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?

The schema already documents the single required 'chain' parameter at 100% coverage, including example values. The description mentions a specific chain but adds no syntax or constraints beyond the schema.

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?

The description states a specific verb and resource: get a wallet address and details for a given chain. It distinguishes itself somewhat from status/balance siblings by focusing on the wallet instance itself, but it does not explicitly name alternatives or scope boundaries.

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

Usage Guidelines2/5

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

The only usage-related guidance is 'Requires login,' which is a precondition rather than a when-to-use rule. It does not explain when to choose this over sibling tools like rift_get_wallet_status, rift_get_balance, or rift_get_user_tokens.

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