Skip to main content
Glama
Rift Finance MCP Server

Rift Finance MCP Server

Official
by Rift-FI

rift_delete_all_recovery

Delete all recovery methods for a Rift Finance account after user confirmation; requires external ID and password to authorize this destructive action.

Instructions

Delete ALL recovery methods. DESTRUCTIVE — confirm with user. Requires login + externalId/password.

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

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.8/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden and does real work: it flags destructiveness, bulk blast radius ('ALL'), the need for user confirmation, and the auth requirement. It stops short of stating reversibility or the consequence of deleting the last recovery method, which is the main remaining risk gap.

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 fragments, front-loaded with the action and scope, then the destructive warning, then prerequisites. Nothing is padded and the highest-risk information appears first.

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 mutation with no annotations and no output schema, the definition covers what an agent needs: what is deleted, that it is destructive, that confirmation is required, and what credentials to supply. Only the outcome of a successful deletion and irreversibility remain unstated.

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%, including a note that password is required by verifyOtp middleware, so the schema already documents both parameters. The description adds only that these constitute login credentials; it adds no format or renewal guidance beyond the schema, so baseline 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 with explicit scope: 'Delete ALL recovery methods.' The capitalized 'ALL' signals bulk scope, which implicitly separates it from the singular rift_remove_recovery_method, but no sibling is named outright.

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?

'DESTRUCTIVE — confirm with user' gives a concrete pre-call procedure and 'Requires login' gives a precondition, so usage is more than implied. However, it never says when to prefer this over the per-method removal sibling or when not to use it, leaving alternative selection to inference.

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