Skip to main content
Glama
Rift Finance MCP Server

Rift Finance MCP Server

Official
by Rift-FI

rift_kyc_job_status

Poll a KYC verification job to check its current status, so you can confirm whether identity verification has completed before proceeding. Requires login and a job ID.

Instructions

Poll the status of a KYC verification job. Requires login.

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": {
      "jobId": "<jobId>"
    },
    "name": "rift_kyc_job_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.0.0

TDQS

B3.1/5.0
Behavior3/5

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

No annotations exist, so the description carries the full descriptive burden. It does disclose the auth requirement ('Requires login') and that this is a polling operation, which is genuine value beyond the schema. It omits, however, what job states can be returned, which states are terminal, and any rate-limit or polling-cadence guidance.

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, verb-first and front-loaded with the core action, with the prerequisite placed after. Nothing is padded, though the extreme brevity is under-specification rather than disciplined concision.

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?

A polling tool with no output schema and no annotations must explain what status values come back and when polling should cease; neither is present. For an async-job status endpoint, the definition leaves the agent unable to interpret results or decide its loop behavior.

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?

There is one required parameter (jobId) at 0% schema description coverage, and the description says nothing about its format, where a jobId comes from, or its relationship to the polled job. The single sentence of text gives the agent no help in supplying a valid jobId.

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: 'Poll the status of a KYC verification job.' That distinguishes it in principle from a one-shot status check, though it never names the sibling rift_kyc_status it most closely resembles, leaving the agent to infer the distinction.

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 'Poll' implies repeated invocation until completion, and 'Requires login' flags a prerequisite. But there is no explicit when-to-use versus rift_kyc_status, no guidance on poll interval or when to stop polling, and no exclusion conditions.

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