mcp-server

start_identity_verification

Start or restart identity verification (KYC) — the first setup step before RealOpen can issue a crypto Proof of Funds letter for a real estate offer. If a previous session exists that was incomplete, denied, or expired, this creates a new one. Returns a secure hosted verification URL the user opens in their browser; do not collect sensitive identity details in chat.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`force_new`	No	Force a new verification session even if one is pending (use after denial or expiry)

Output Schema

TableJSON Schema

Name	Required	Description
`status`	Yes	One of: already_verified, processing, redirect_required
`message`	No
`instructions`	No
`verified_name`	No	Set when status=already_verified
`previous_status`	No	The prior session status if this call is restarting a stale session
`verification_url`	No	Stripe Identity URL the user opens in their browser. Present when status=redirect_required.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 1, 2026

removedInput schema / properties / id_number_required

Removed value: -{
-  "default": true,
-  "description": "Whether to require an ID number on the document (default: true)",
-  "type": "boolean"
-}

Changed1 schema field changedMay 9, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "instructions": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "message": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "previous_status": {
+      "description": "The prior session status if this call is restarting a stale session",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "status": {
+      "description": "One of: already_verified, processing, redirect_required",
+      "type": "string"
+    },
+    "verification_url": {
+      "description": "Stripe Identity URL the user opens in their browser. Present when status=redirect_required.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "verified_name": {
+      "description": "Set when status=already_verified",
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "status"
+  ],
+  "type": "object"
+}

First observedApr 14, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Adds real behavioral context beyond the annotations: it returns a hosted verification URL the user opens in a browser, it re-creates sessions after denial/expiry (consistent with idempotentHint=false), and it warns not to collect identity details in chat. It does not cover auth/permission requirements or rate limits, so not a 5.

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?

Three sentences, front-loaded with the core action and workflow position, then restart semantics, then the security caveat. Every sentence is relevant, though the middle sentence overlaps somewhat with what the schema says about force_new.

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

Completeness5/5

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

With an output schema present, return values need not be explained, and the description still covers flow position, restart behavior, and safe handling of the hosted URL. Nothing an agent needs to call this correctly is missing.

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% and the single force_new parameter is fully documented there, so baseline is 3. The description's mention of restarting after incomplete/denied/expired sessions loosely reinforces force_new's purpose but adds no syntax or format detail beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource ('Start or restart identity verification (KYC)') and immediately places it in the workflow as 'the first setup step before RealOpen can issue a crypto Proof of Funds letter.' An agent can distinguish it from siblings like generate_proof_of_funds or refresh_wallet_verification without opening the schema.

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

Usage Guidelines4/5

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

Gives clear usage context: it is the prerequisite step for a Proof of Funds letter, and a new session is created if a prior one was incomplete, denied, or expired. It does not name an explicit alternative tool or a when-not-to-use condition, so it stops short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All mcp-server tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.