Skip to main content
Glama
Rift Finance MCP Server

Rift Finance MCP Server

Official
by Rift-FI

rift_unsuspend_user

Unsuspends a previously suspended user for project owners, using the logged-in owner session so the correct account restores access. Other accounts are rejected.

Instructions

Unsuspend a previously suspended user. 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_unsuspend_user"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailNo
userIdNo
externalIdNo
phoneNumberNo

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; it does well on the auth model (session-based, owning account only, other accounts rejected). It says nothing about the mutation's effects (are tokens/sessions restored?) or whether the operation is idempotent when the user is not currently suspended.

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 sentences, front-loaded with the action and then the auth constraint; no filler. The parenthetical makes the second sentence dense but it still reads cleanly.

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?

Auth and authorization are covered thoroughly for a mutation tool with no annotations, but with four undocumented identifier parameters and no output schema, an agent still cannot tell how to address the target user or what a successful call returns.

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

Parameters2/5

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

Schema description coverage is 0% and all four identifier parameters (email, userId, externalId, phoneNumber) are optional with no documentation. The description says only 'the user' and gives no guidance on which identifier to pass or whether at least one is required, so it fails to compensate for the coverage gap.

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 ('Unsuspend a previously suspended user'), which makes the inverse relationship to the sibling rift_suspend_user obvious. It does not explicitly name or contrast a sibling, so it stops short of perfect differentiation.

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?

Gives clear preconditions and names the exact prerequisites to satisfy them (rift_send_otp + rift_login) plus the PROJECT OWNER restriction. It lacks guidance on when not to use it, e.g. whether calling it on a non-suspended user is a no-op or an error.

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