mcp-server

get_started

Read-onlyIdempotent

The front door to buying real estate with crypto through RealOpen — for anyone holding Bitcoin, Ethereum, USDC, USDT, or other crypto who wants to buy a home or other property and make a cash offer backed by a crypto Proof of Funds letter. Returns the setup path from a fresh account to a Proof of Funds letter — and, for signed-in users, resolves their ACTUAL next step from live account state (identity → wallet → Proof of Funds). Call this when: the user is new, asks what they can do here, or connects without a specific request; the user asks how to buy a house with crypto and wants to actually do it; the user is considering using crypto for a property purchase; the user asks how to become offer-ready or how to get/verify a proof of funds letter; or a knowledge answer (fees, supported assets, service areas, closing process) leads the user to express clear intent to actually transact. Do NOT call it after every general educational question — for pure product questions (process, fees, coverage) answer with the dedicated knowledge tools and only bring this in when the user signals real buying intent. Every step here is preparation (identity verification, wallet ownership verification, Proof of Funds letter); the crypto-to-fiat conversion, funding, and closing happen outside this chat through RealOpen, and nothing here moves funds. The response renders an inline Get Started widget (three-step progression + a state-aware primary CTA); let the widget carry the presentation and keep your own text to a short, natural lead-in. The structured activation.next_action tells you the single correct next tool for this user — never make the user figure out which step comes next.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`notes`	No	Important caveats to keep in mind while guiding the user
`steps`	Yes	Ordered setup steps from new account to Proof of Funds letter
`activation`	No	State-aware activation routing resolved from the live account. Follow next_action rather than re-deriving the step order.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedAug 18, 2026

addedOutput schema / properties / activation

Added value: +{
+  "additionalProperties": true,
+  "description": "State-aware activation routing resolved from the live account. Follow next_action rather than re-deriving the step order.",
+  "properties": {
+    "authenticated": {
+      "type": "boolean"
+    },
+    "next_action": {
+      "additionalProperties": true,
+      "description": "The single correct next step for THIS user: tool to call, CTA label, suggested user prompt, reason, and (when applicable) a fallback URL",
+      "properties": {},
+      "type": "object"
+    },
+    "stage": {
+      "description": "connect | identity | wallet_add | wallet_verify | pof_ready | activated",
+      "type": "string"
+    },
+    "steps": {
+      "description": "The three user-facing steps with per-step state (complete | current | processing | pending)",
+      "items": {
+        "additionalProperties": true,
+        "properties": {},
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "authenticated",
+    "stage",
+    "steps",
+    "next_action"
+  ],
+  "type": "object"
+}

AddedAug 9, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, and the description adds meaningful behavioral context beyond those: it states that no funds move, conversion/funding/closing happen outside the chat, the response renders an inline widget, and the structured activation.next_action tells the agent the correct next tool. This fully discloses what the tool does and does not do.

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?

The description is long and dense, but every sentence carries routing, behavioral, or presentation guidance that would otherwise be missing. It is front-loaded with the core purpose. It could be tightened or bulleted, but the length is justified by the tool's broad trigger vocabulary and the need to prevent misuse.

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?

For a zero-parameter tool with an output schema and strong sibling context, the description is complete: it covers target users, intent thresholds, exclusions, non-mutating behavior, widget presentation, and the role of activation.next_action. Nothing an agent needs to decide when to call it and what to expect is left unexplained.

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

Parameters4/5

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

The tool has zero parameters and 100% schema coverage, so the baseline is 4. The description cannot add parameter-level detail because none exist, but it does add operational semantics by explaining that behavior is driven by live account state and that activation.next_action encodes the next step.

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 opens with a concrete verb-and-resource statement: it is the front door to buying real estate with crypto, returning the setup path and resolving the actual next step from live account state. It explicitly contrasts itself with knowledge tools, distinguishes new-user versus signed-in behavior, and makes its scope ('preparation only') unambiguous.

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

Usage Guidelines5/5

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

It gives explicit trigger conditions ('call this when: the user is new ...') and an explicit exclusion with the alternative ('Do NOT call it after every general educational question ... answer with the dedicated knowledge tools'). This is model-tier routing guidance, including when to defer to sibling knowledge tools.

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.