Skip to main content
Glama
Rift Finance MCP Server

Rift Finance MCP Server

Official
by Rift-FI

rift_kyc_is_verified

Checks whether the currently logged-in user has completed KYC verification, helping AI assistants confirm eligibility before enabling Rift Finance account actions that require verification.

Instructions

Check if the currently logged-in user is KYC verified. Requires login.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.0.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden; it does disclose the authentication requirement, which is genuine behavioral context. However, it says nothing about what is returned (a boolean flag?), what happens without a session, or whether the check is cached/rate-limited.

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 with the core action first and the precondition second; there is no filler or redundancy.

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 parameterless read-only check this is nearly complete: the actor scope and login requirement are covered. The one remaining gap is that no output schema exists, yet the description does not state that the result is a verification boolean, leaving the return shape implicit.

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 explain and the baseline of 4 applies. The description correctly avoids inventing arguments the schema does not have.

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 gives a specific verb and resource: checking the KYC verification status of the currently logged-in user. The 'currently logged-in user' scope implicitly separates it from user-targeted siblings like rift_kyc_check_user_exists, but no sibling is named explicitly.

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 states a precondition ('Requires login') that tells the agent when the call is applicable, but offers no explicit when-to-use/when-not guidance or contrast with rift_kyc_status or rift_kyc_verify. Usage is left to inference from the tool name.

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