Skip to main content
Glama
Rift Finance MCP Server

Rift Finance MCP Server

Official
by Rift-FI

rift_get_wallet_status

Check passkey wallet status to see mode, wallet address, passkey count, per-chain owner mode, and whether passkey setup is required before signing.

Instructions

Passkey wallet status: mode (none | legacy | passkey), walletAddress, passkeyCount, per-chain owner mode and needsPasskeySetup. If needsPasskeySetup is true the user must create a passkey in the Rift app before anything can be signed (see rift_guide 'passkey'). If passkeyCount is 1, suggest adding a second passkey for recovery. 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_wallet_status"
  }
}

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. It discloses the login requirement and a meaningful dependency chain (no signing is possible until a passkey exists), plus a pointer to rift_guide 'passkey' for setup detail. It does not say what happens when mode is 'none', whether an error is returned for an unauthenticated caller, or what the per-chain owner mode values mean, which leaves real behavioral gaps for an auth-gated tool.

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?

Three sentences, each doing distinct work: field inventory first, then the blocking condition, then the recovery suggestion, with the auth note last. The parentheses and inline enum are dense but readable; nothing is redundant, though the final 'Requires login' would read better front-loaded with the other preconditions.

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?

Since there is no output schema, the description must describe return values, and it does so field by field with enum values for the most important one. For a zero-parameter, auth-gated status read this is close to complete; the main shortfall is the absence of any stated behavior for the 'none' wallet mode or for unauthenticated calls.

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 baseline is 4 and there is nothing for the description to disambiguate. The field enumeration in the description serves as the de facto output contract, which is a reasonable substitute given no output schema exists.

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 definition names a specific resource (passkey wallet status) and enumerates exactly what it returns: mode with its value set (none | legacy | passkey), walletAddress, passkeyCount, per-chain owner mode, and needsPasskeySetup. It does not explicitly distinguish itself from near-neighbours such as rift_get_wallet_instance or rift_get_user_status, so an agent must still infer the boundary, but the read purpose itself is unambiguous.

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?

There is no 'call this when...' or 'use X instead' statement, so the trigger for invoking the tool versus the wallet-instance or user-status siblings is left implicit. What the description does supply is downstream guidance on acting on the result (create a passkey in the Rift app if needsPasskeySetup is true, suggest a second passkey when passkeyCount is 1), which is useful but is interpretation rather than invocation guidance.

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