Skip to main content
Glama
Rift Finance MCP Server

Rift Finance MCP Server

Official
by Rift-FI

rift_verify_otp

Verify an OTP code without logging in to validate standalone one-time passcodes when login or transaction flows do not handle verification.

Instructions

Verify an OTP code WITHOUT logging in. Rarely needed — for login, use rift_login directly (it verifies OTP internally). For transactions/offramp, pass otpCode directly to rift_send_crypto/rift_offramp. Only use this for standalone OTP checks.

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": {
      "code": "<code>"
    },
    "name": "rift_verify_otp"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesThe OTP code from the user
emailNoEmail the OTP was sent to
phoneNoPhone the OTP was sent to

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.0.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description still discloses the key behavioral trait: this performs a check without establishing a session, so the caller should not expect to be authenticated afterward. It does not say what a verification response contains, whether a code is consumed after a successful check, or how failures surface, leaving a modest gap for a zero-annotation tool.

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 definition, then the exclusion, then the narrow use case. No filler or repetition.

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 simple three-parameter verification tool with full schema coverage, the routing guidance is complete. The only shortfall is that with no output schema, the description does not indicate what a successful or failed verification returns.

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 code/email/phone are already documented in the schema; the description adds nothing about their semantics, such as whether email or phone should accompany code or how the channel is selected. Baseline 3 is appropriate when the schema carries parameter meaning.

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 (verify an OTP code) plus a defining constraint ('WITHOUT logging in') that separates it from rift_login and the transaction tools. An agent can identify the tool's job from the first clause alone.

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 says it is 'rarely needed', names the alternative for login (rift_login, which verifies internally), and names the alternative for transactions (pass otpCode to rift_send_crypto/rift_offramp). Covers when-to-use and when-not-to-use with concrete routing.

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