Skip to main content
Glama
Rift Finance MCP Server

Rift Finance MCP Server

Official
by Rift-FI

rift_delete_user

Permanently deletes a user account and all associated data. Use only after confirming with the user twice, as the action is irreversible.

Instructions

PERMANENTLY delete user account and all data. DESTRUCTIVE — confirm with user TWICE before calling.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "rift_delete_user"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailNo
otpCodeNo
passwordNo
externalIdNo
phoneNumberNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.0.0

TDQS

B3.1/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. It does disclose the two most important traits: the deletion is permanent and removes all data, and a double confirmation is required. It omits operational behavior that matters for a 5-credential write tool — whether password/OTP must accompany the call, whether the action is reversible by support, and what happens on partial identifiers.

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, zero waste, with the destructive scope front-loaded ahead of the operational warning. Capitalization is used deliberately to flag risk rather than padding the text.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a five-parameter, zero-required, unannotated destructive tool with no output schema, the description is too thin. An agent still cannot determine the required identity/credential combination or the failure modes, so it is not complete enough to invoke safely without guessing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across five parameters (email, otpCode, password, externalId, phoneNumber) and none are required. The description mentions no parameter at all, so the agent gets no help deciding which identifier to supply or which credentials must be paired with it — a critical ambiguity for an irreversible operation.

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: 'PERMANENTLY delete user account and all data'. The word 'PERMANENTLY' implicitly distinguishes this from reversible siblings like rift_suspend_user, but no sibling is named and the basis of identification (email vs externalId vs phone) is not stated.

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?

Gives one concrete pre-call condition ('confirm with user TWICE before calling'), which is real usage guidance. However it offers no alternative routing — nothing tells the agent to prefer rift_suspend_user or rift_delete_all_recovery in softer scenarios — so the when-to-use-vs-alternatives dimension is only implied.

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