Skip to main content
Glama
Rift Finance MCP Server

Rift Finance MCP Server

Official
by Rift-FI

rift_kyc_status

Check KYC verification status by email, external ID, or phone number to see whether a user is verified, pending, failed, or provisional—without authentication.

Instructions

Check KYC verification status. Returns: verified, pending, failed, or provisional. No auth required.

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

Input Schema

NameRequiredDescriptionDefault
emailNo
externalIdNo
phoneNumberNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.0.0

TDQS

B3/5.0
Behavior3/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; it does usefully disclose the auth requirement and enumerates the four possible outcomes. It does not explain what happens when identifiers are omitted, whether the lookup falls back to the caller's identity, or how lookup failures are reported.

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 short sentences, front-loaded with the purpose and followed by the return enumeration and auth note. Nothing is wasted, though the terseness leaves substantive gaps rather than covering them.

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?

The return values and no-auth note cover part of what an agent needs, and the absence of an output schema is partly offset by the listed status values. However, the zero-coverage parameter set and lack of annotations leave key behavior, particularly how the three lookup identifiers interact, undocumented.

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?

Three optional parameters exist with 0% schema description coverage, and the description adds no meaning for email, externalId, or phoneNumber. It never says whether these are alternative lookup keys, whether one is preferred, or what occurs when none are supplied, so the description fails to compensate for the schema 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?

The description gives a specific verb and resource ('Check KYC verification status') and adds the possible return states, so the resource is unambiguous. It does not differentiate itself from close siblings such as rift_kyc_is_verified or rift_kyc_job_status, leaving an agent to guess which status check to call.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description states no when-to-use conditions, prerequisites, or alternatives despite several sibling KYC tools that appear to overlap. The only contextual guidance is 'No auth required', which is about authentication rather than tool selection.

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