Skip to main content
Glama
Rift Finance MCP Server

Rift Finance MCP Server

Official
by Rift-FI

rift_get_my_recovery_methods

Fetch the current user's account recovery methods after verifying their external ID and password.

Instructions

Get the current user's recovery methods. Requires login + externalId/password for verification.

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>",
      "password": "<password>"
    },
    "name": "rift_get_my_recovery_methods"
  }
}

Input Schema

NameRequiredDescriptionDefault
passwordYesUser password (required by verifyOtp middleware)
externalIdYesUser external ID

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 and does disclose the auth/verification requirement, including the externalId/password check. It says nothing about error behavior on failed verification, rate limits, or what the returned methods look like, so behavioral disclosure is partial.

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?

Two short sentences, purpose first then prerequisite, with no filler. Every clause carries information the agent can act on.

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 two-parameter read tool with full schema documentation and no output schema, this covers the essentials: what is fetched, for whom, and what credentials are required. Only failure-mode and return-shape details are absent, which is a minor gap at this complexity.

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 both parameters are documented, including the note that password is required by the verifyOtp middleware. The description adds little beyond restating that both values are needed for verification, so the baseline of 3 applies.

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 the current user's recovery methods.' The word 'my' scopes it to the authenticated user, which separates it from broader siblings like rift_get_recovery_options, though no sibling is named explicitly.

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?

The description implies a read of the caller's own recovery methods and states a prerequisite ('Requires login + externalId/password for verification'), which is useful context. It does not say when to prefer this over rift_get_recovery_options or the other recovery tools, so the agent must infer the distinction.

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