Skip to main content
Glama
Rift Finance MCP Server

Rift Finance MCP Server

Official
by Rift-FI

rift_get_user_status

Look up a user and check suspension status using the logged-in project owner session. Rejects requests from accounts that do not own the project.

Instructions

Look up a user and check whether they are suspended. 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_get_user_status"
  }
}

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
Behavior4/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it does disclose the key trait: this reads via the logged-in session and only succeeds for the project-owning account, with others rejected. It omits the read-only nature and any failure/lookup-miss behavior, keeping it below a 5.

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, purpose front-loaded, no padding. 'Other accounts are rejected' mildly restates 'PROJECT OWNER only', but the redundancy is minor and the length is well matched to the content.

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 ownership are fully covered, which is the hard part, and there is no output schema to explain. But for a four-param, zero-coverage lookup tool with no annotations, the description leaves the identifier-selection question and the shape of the suspension result (boolean vs. status object) entirely unaddressed.

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?

Four parameters (email, userId, externalId, phoneNumber) with 0% schema description coverage and no required fields, yet the description never says which identifier to supply or whether they are alternatives. With zero structured documentation, the description should have compensated for the identifier-selection ambiguity and does not.

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?

Names a specific verb+resource ('Look up a user') plus a specific facet ('check whether they are suspended'), which distinguishes it from the plain rift_get_user and from rift_get_suspended_users. It stops short of naming the sibling it overlaps with, so the differentiation is inferred rather than 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?

The auth precondition is spelled out precisely (owner session required, other accounts rejected, prerequisite rift_send_otp + rift_login flow). However, there is no guidance on when to prefer this over rift_get_user or rift_get_user_tokens, and no exclusions – the usage context is implied rather than declared.

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