Skip to main content
Glama
Rift Finance MCP Server

Rift Finance MCP Server

Official
by Rift-FI

rift_get_recovery_options

Retrieve available account recovery options for locked-out users without login, showing masked email and phone details to help them regain access.

Instructions

Get available recovery options for a user. Shows masked email/phone. Does NOT require login — for users who are locked out.

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": {
      "externalId": "<externalId>"
    },
    "name": "rift_get_recovery_options"
  }
}

Input Schema

NameRequiredDescriptionDefault
externalIdYesThe user's external ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.0.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the whole burden and does disclose two non-obvious traits: the call needs no authentication, and returned contact data is masked (email/phone). It omits error behavior (unknown externalId), rate limits, and whether results are empty vs an error when no recovery methods exist.

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 clauses, front-loaded with purpose, then output privacy, then the auth exemption. No filler and nothing buried.

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 single-parameter read tool with no output schema, the description covers purpose, caller context, and data-masking behavior. It could say more about what a "recovery option" actually contains, but an agent has enough to select and invoke it correctly.

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 coverage is 100% and externalId is documented in the schema as "The user's external ID," so the description adds nothing about the parameter. Baseline 3 is appropriate when the schema already does this work.

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?

States a specific verb and resource ("Get available recovery options for a user") and scopes it to a different audience than rift_get_my_recovery_methods via "for a user." It is clear what the tool does, though it never names the sibling it most resembles, leaving the self-vs-other distinction implicit.

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?

"For users who are locked out" gives a concrete triggering condition, and "Does NOT require login" clarifies that this is callable in an unauthenticated support flow. No alternatives are named and no exclusions are stated, so it stops short of full routing 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