Skip to main content
Glama
Rift Finance MCP Server

Rift Finance MCP Server

Official
by Rift-FI

rift_kyc_get_token

Initiates KYC verification and returns a URL the user must visit to complete identity checks. Provide an email, phone, or external ID plus ISO country code.

Instructions

Start KYC verification — returns a verification URL the user must visit. No auth required.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "country_code": "<country_code>",
      "identifier": "<identifier>"
    },
    "name": "rift_kyc_get_token"
  }
}

Input Schema

NameRequiredDescriptionDefault
identifierYesUser's email, phone, or externalId
country_codeYesISO country code: KE, NG, UG, GH, ET, etc

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.0.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations at all, the description carries the full disclosure burden and does deliver two genuinely useful facts: no auth is required and the output is a URL the user must navigate to. It omits what an agent would want for a flow-initiating call — whether repeated calls create duplicate sessions, what happens with an already-verified user, whether the URL expires, and what errors arise from an unsupported country_code.

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, zero filler, with the action and its user-facing consequence front-loaded and the auth constraint attached last. Nothing could be removed without losing information.

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 two-parameter tool with no output schema, the description supplies the two things an agent cannot get from structured fields: the return value is a URL requiring user action, and no auth is needed. Idempotency, expiry and error behavior remain undeclared, which is the main remaining gap.

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

Parameters3/5

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

Schema description coverage is 100%: 'identifier' is documented as email/phone/externalId and 'country_code' as an ISO code with examples. The description adds nothing about these parameters, so the schema does all the work — the baseline 3 applies.

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 plus resource ('Start KYC verification') and adds the concrete outcome ('returns a verification URL the user must visit'), which separates it from the read-only siblings like rift_kyc_is_verified, rift_kyc_status and rift_kyc_job_status. It does not name those siblings explicitly, so the differentiation is implied by the verb 'Start' 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 word 'Start' and the instruction that the URL 'must be visited' imply this is the entry point of the KYC flow, and the surrounding rift_kyc_* siblings suggest follow-up status checks. However, there is no explicit when-to-use/when-not guidance, no statement of whether to call this before or after rift_kyc_check_user_exists, and no mention of handling users already mid-verification.

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