Skip to main content
Glama
Rift Finance MCP Server

Rift Finance MCP Server

Official
by Rift-FI

rift_login

Authenticate with Rift Finance using email/phone OTP or external ID/password, then store the session so subsequent authenticated tool calls work without logging in again.

Instructions

Login to Rift. Stores the session so all authenticated tools work. Three methods: (1) email + otpCode — call rift_send_otp first, (2) phoneNumber + otpCode — call rift_send_otp first, (3) externalId + password — no OTP needed. After login, you do NOT need to login again for subsequent tool calls in this session.

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

Input Schema

NameRequiredDescriptionDefault
emailNoEmail (pair with otpCode)
otpCodeNoOTP code from rift_send_otp
passwordNoPassword (pair with externalId)
externalIdNoExternal ID (pair with password)
phoneNumberNoPhone (pair with otpCode)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.0.0

TDQS

A4.2/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full disclosure burden, and it does reveal the key side effect (persisting a session that unlocks other tools) and the persistence guarantee for subsequent calls. It omits failure behavior, whether an existing session is overwritten, and anything about session expiry or credential handling — meaningful gaps for an auth mutation.

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?

Front-loaded with purpose and effect, then a compact numbered list of the three methods with their prerequisites. No filler sentences; every clause conveys a distinct operational fact.

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?

Given five optional parameters, no required fields, no output schema, and no annotations, the description supplies enough to construct a valid call in any of the three modes. Only the session/error edge cases and sibling-selection rule are left unstated.

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?

Schema coverage is 100%, so individual parameter descriptions are already handled by the schema. The description adds real cross-parameter meaning by defining the three valid pairings (email+otpCode, phoneNumber+otpCode, externalId+password), which the per-field schema text only partially conveys.

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 ("Login to Rift") and immediately explains the effect: it stores the session so authenticated tools work. Enumeration of the three supported credential combinations distinguishes it from rift_login_apple and rift_login_google without needing their schemas.

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

Usage Guidelines4/5

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

Explicitly sequences usage: OTP methods require calling rift_send_otp first, the password method does not, and re-login is unnecessary within a session. It does not, however, say when to choose this tool over the sibling OAuth-style logins (rift_login_apple / rift_login_google), leaving that comparison implicit.

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