Skip to main content
Glama
Rift Finance MCP Server

Rift Finance MCP Server

Official
by Rift-FI

rift_suspend_user

Suspend a platform user by providing their identifier and reason. Requires a logged-in project owner session; other accounts are rejected.

Instructions

Suspend a user from the platform. PROJECT OWNER only: uses the logged-in session, so the user must be logged in (rift_send_otp + rift_login) as the account that owns this project. Other accounts are rejected.

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

Input Schema

NameRequiredDescriptionDefault
emailNoUser email
reasonNoReason for suspension
userIdNoUser database ID
externalIdNoUser external ID
phoneNumberNoUser phone

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.0.0

TDQS

B3.4/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 it does disclose the session-based auth model and that non-owner accounts are rejected — meaningful behavioral context. It omits what suspension actually does to the user (blocks login? freezes funds? reversible?), which is the key behavioral fact for a mutation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences with the core action front-loaded and the auth constraint following immediately. No wasted wording; the parenthetical login flow is compact and useful.

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

Completeness3/5

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

No output schema and no annotations, so the description must stand alone. It covers authentication and authorization well but leaves the effect of suspension, its reversibility, and the required-identifier question unaddressed for a five-parameter mutation tool.

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 the baseline is 3. That said, the five optional identifiers (email, userId, externalId, phoneNumber) with zero required parameters create real ambiguity about which one must be supplied, and the description adds no clarification.

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?

The description states a specific verb and resource ('Suspend a user from the platform') and implicitly contrasts with rift_unsuspend_user and rift_delete_user through the verb choice. It stops short of explicitly naming those siblings or clarifying that suspension differs from deletion.

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?

It gives a real precondition chain: you must be PROJECT OWNER, logged in via rift_send_otp + rift_login. But it offers no guidance on when to suspend rather than delete (rift_delete_user) or when to unsuspend, so the choice among account-state tools is left 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