Skip to main content
Glama

mcp-server

by io.github.realopengroup
OverviewDiscussionsAdmin

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 URL the user must open in their browser.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
force_newNoForce a new verification session even if one is pending (use after denial or expiry)
id_number_requiredNoWhether to require an ID number on the document (default: true)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
statusYesOne of: already_verified, processing, redirect_required
messageNo
instructionsNo
verified_nameNoSet when status=already_verified
previous_statusNoThe prior session status if this call is restarting a stale session
verification_urlNoStripe Identity URL the user opens in their browser. Present when status=redirect_required.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • 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"
+}
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already indicate this is a state-changing, non-idempotent operation, and the description adds valuable behavioral specifics: it creates a new session when a prior one is incomplete/denied/expired and returns a URL the user must open. This goes beyond what the annotations alone convey.

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?

Three sentences, each earning its place: what the tool does, when a restart happens, and what the output is. The most important action is front-loaded and no filler is present.

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?

The description covers the tool's role in the broader workflow, restart behavior, and output format. An output schema exists, so detailed return values are not required, and the parameter schema fully documents the inputs. An agent has enough to invoke it correctly.

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%, so the schema already documents force_new and id_number_required clearly. The description adds no parameter-level meaning, but it does provide relevant session context that indirectly supports force_new. Baseline 3 is appropriate.

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?

The description uses a specific verb and resource: 'Start or restart identity verification (KYC)', and grounds it in the RealOpen flow as 'the first setup step before... a crypto Proof of Funds letter'. This clearly distinguishes it from sibling tools like generate_proof_of_funds and verify_wallet_signature.

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?

It clearly states when to use the tool: as the first KYC setup step, and when restarting after an incomplete, denied, or expired session. It does not explicitly name alternatives or exclusion conditions, but the context is strong enough for an agent to select it appropriately.

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

All mcp-server toolsInspect
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.

Resources