Skip to main content
Glama
Rift Finance MCP Server

Rift Finance MCP Server

Official
by Rift-FI

rift_get_suspended_users

List all suspended users in a project to review restricted accounts; requires the logged-in project owner's session.

Instructions

List all suspended users in the project. 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_suspended_users"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.0.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations supplied, the description carries the disclosure burden and does so for the highest-risk aspect: it states this uses the logged-in session, requires project-owner privileges, and that other accounts are rejected. It leaves out secondary traits such as whether results are paginated, what happens for a project with no suspended users, and the shape of returned records.

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: purpose first, then authorization constraint. Every clause earns its place, and the critical 'PROJECT OWNER only' restriction is front-loaded rather than buried.

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 zero-argument, read-only listing tool with no annotations and no output schema, the description covers purpose and the full auth prerequisite, which is what an agent needs to call it successfully. A brief note on return contents or empty-list behavior would make it complete, but the omission is low-risk.

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

Parameters4/5

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

The tool takes zero parameters, so there is no parameter semantics to add; per the baseline for a 0-param schema this scores 4. The description correctly implies the project scope is derived from the session rather than from an argument, which is the only meaningful parameter-adjacent fact here.

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 opens with a specific verb+resource: 'List all suspended users in the project', which is unambiguous about what the tool returns and its project-level scope. It does not explicitly contrast itself with the per-user lookups among its siblings (e.g. rift_get_user_status), so it falls just short of a 5.

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?

It gives a clear precondition for use: the caller must be logged in as the project owner, and it names the two tools that establish that session (rift_send_otp + rift_login). It does not state when to prefer this over other user-listing/lookup calls, but the auth context is explicit and actionable.

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