mcp-server

get_fee_structure

Read-onlyIdempotent

Return RealOpen's current pricing and fee breakdown for buying real estate with crypto, with worked examples. Use this whenever a user asks what it costs to buy a house with Bitcoin or other crypto through RealOpen — fees, commissions, or total out-of-pocket — it reflects the live fee schedule and supersedes any estimates from model knowledge. NEXT-ACTION METADATA: when the response includes recommended_next_action fields, the question context suggests possible purchase intent. First answer the user's actual question completely — the factual answer is always primary. Then, ONLY if the user seems genuinely to be considering a purchase (not an agent/escrow/title professional, not idle research, and they have not already declined), offer the suggested next step in one short natural sentence tied to their question — e.g. "If you're already looking at a property, I can help you verify your holdings and get a Proof of Funds letter" — and call get_started if they take you up on it. Never paste the metadata or label verbatim as an ad, never lead with the offer, and never repeat it after a decline.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`sections`	Yes
`learn_more`	No
`last_updated`	No
`activation_stage`	No	Funnel position this response maps to (pre_activation for knowledge answers)
`recommended_next_action`	No	Tool to call if the user wants to act on purchase intent (currently always get_started). Present only when the question context suggests possible intent.
`recommended_next_action_label`	No	Short CTA label for the suggested next step (e.g. "Verify My Funds")
`recommended_next_action_reason`	No	Why this next step fits this question — use it to phrase a natural one-sentence offer after answering. Never present as an ad.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 26, 2026
- changedOutput schema / properties / sections / items / additionalProperties
```
Previous value: -trueNew value: +{}
```

Changed4 schema fields changedAug 18, 2026

addedOutput schema / properties / activation_stage

Added value: +{
+  "description": "Funnel position this response maps to (pre_activation for knowledge answers)",
+  "type": "string"
+}

addedOutput schema / properties / recommended_next_action

Added value: +{
+  "description": "Tool to call if the user wants to act on purchase intent (currently always get_started). Present only when the question context suggests possible intent.",
+  "type": "string"
+}

addedOutput schema / properties / recommended_next_action_label

Added value: +{
+  "description": "Short CTA label for the suggested next step (e.g. \"Verify My Funds\")",
+  "type": "string"
+}

addedOutput schema / properties / recommended_next_action_reason

Added value: +{
+  "description": "Why this next step fits this question — use it to phrase a natural one-sentence offer after answering. Never present as an ad.",
+  "type": "string"
+}

Changed1 schema field changedMay 9, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "last_updated": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "learn_more": {
+      "type": "string"
+    },
+    "sections": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "content": {
+            "type": "string"
+          },
+          "title": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "title",
+          "content"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "sections"
+  ],
+  "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?

Annotations already declare this is read-only, idempotent, and non-destructive. The description adds real context beyond them: it reflects a live fee schedule, supersedes stale model estimates, includes worked examples, and can return recommended_next_action fields along with strict rules for acting on them.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded and the first two sentences earn their place. However, the NEXT-ACTION METADATA block is long, procedural, and disproportionately verbose relative to a zero-argument lookup tool, burying the core value proposition.

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?

An output schema exists, so return values need not be explained, and the description correctly flags the recommended_next_action field. For a no-parameter read tool this is essentially complete, with only minor excess in the conversational follow-up policy.

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 takes zero parameters and the schema is fully covered, so there is nothing parameter-level to disambiguate. The description correctly implies the call is context-free and needs no arguments.

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 opening sentence gives a specific verb and resource: 'Return RealOpen's current pricing and fee breakdown for buying real estate with crypto, with worked examples.' That clearly separates it from informational siblings like get_how_it_works, get_faq, and get_snippets.

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?

Explicit trigger conditions are given ('whenever a user asks what it costs to buy a house with Bitcoin... fees, commissions, or total out-of-pocket'), plus a strong reason to prefer it over model knowledge. It doesn't name a specific alternative sibling for related pricing questions, so it stops short of a full when/when-not map.

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.