Skip to main content
Glama
Rift Finance MCP Server

Rift Finance MCP Server

Official
by Rift-FI

rift_kyc_check_user_exists

Verify user existence and KYC status by email, external ID, or phone number; no authentication is required.

Instructions

Check if a user exists and their KYC status. 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_check_user_exists"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailNo
externalIdNo
phoneNumberNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.0.0

TDQS

C2.9/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden, and it does contribute one useful behavioral fact: no auth is required. However, it omits what happens when no identifier is supplied, whether lookups are exact-match, and what the response contains (existence flag plus status), leaving meaningful behavioral gaps for an unannotated read tool.

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, front-loaded sentences with no filler. It is efficient, though the brevity comes partly at the cost of the identifier guidance an agent actually needs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool takes three undocumented optional parameters with no annotations and no output schema, so the description is the only source of semantics. It covers purpose and auth, but leaves identifier selection and return shape entirely unstated, which is not enough for this schema.

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 three parameters (email, externalId, phoneNumber) are undocumented in the schema, so the description must compensate. It instead never mentions any parameter, so an agent cannot tell which identifier to pass, whether they are alternatives or combinable, or that at least one is presumably needed.

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: checks whether a user exists and returns their KYC status. It is clear enough to distinguish from mutation siblings like rift_delete_user or rift_suspend_user, but it does not explicitly position itself against near-neighbors such as rift_kyc_is_verified or rift_kyc_status.

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?

There is no when-to-use guidance and no mention of alternatives among the many KYC siblings. It also gives no indication of whether one, two, or all three identifiers are expected, which matters because the schema marks zero parameters as required.

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