Skip to main content
Glama
Rift Finance MCP Server

Rift Finance MCP Server

Official
by Rift-FI

rift_signup

Create a new Rift Finance account using email or phone with an OTP code, or an externalId with a password. Run this before logging in with the same credentials.

Instructions

Create a new Rift user account. Two ways: (1) email or phone sign-up: FIRST call rift_send_otp for that email/phone, ask the user for the code, then call this with email (or phoneNumber) + displayName + otpCode. Afterwards call rift_login with the SAME otpCode (no new code needed). (2) externalId + password sign-up: no OTP needed. After signup the user still has to log in via rift_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": {
      "displayName": "<displayName>"
    },
    "name": "rift_signup"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailNoUser email. For an email sign-up pair it with otpCode
otpCodeNoOTP from rift_send_otp, sent to the email/phone being registered. Required for email/phone sign-up on servers that enforce it, and always accepted, so send it. Reuse the SAME code for rift_login right after.
passwordNoUser password (required with externalId)
externalIdNoUnique user ID in your system (externalId + password sign-up)
displayNameYesDisplay name
phoneNumberNoUser phone with country code. For a phone sign-up pair it with otpCode

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.0.0

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose key behavior: prerequisite OTP step, that the same OTP is reused for login, and that sign-up does not authenticate the user. It omits error/duplicate-account behavior and any permission or rate-limit context, keeping it below 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Numbered flows make the sequencing easy to scan and every sentence carries operational content. It is somewhat dense with repeated OTP guidance across description and schema, but nothing is wasted.

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 six-parameter mutation with no output schema and no annotations, the description covers prerequisites, sequencing, and post-conditions well. The main gap is that it does not indicate what the call returns (e.g. user id or session state), which matters since no output schema exists.

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 already 100%, so the baseline is 3; the description goes further by explaining the two parameter combinations (email/phoneNumber + otpCode vs externalId + password) and the OTP reuse semantics, which the schema only hints at.

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?

Opens with a specific verb+resource: 'Create a new Rift user account.' It immediately distinguishes itself from rift_login and rift_send_otp by describing the two sign-up paths and where those siblings fit in the sequence.

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 lays out two flows with ordering: OTP path requires calling rift_send_otp first, asking the user for the code, then calling this tool; externalId+password path needs no OTP. It also states the follow-up action (call rift_login with the SAME otpCode).

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