Skip to main content
Glama
Sign In

mcp-server

by io.github.realopengroup
OverviewDiscussionsAdmin

get_faq

Read-onlyIdempotent

Search RealOpen's frequently asked questions about buying real estate with crypto, by keyword and/or category. Use this when a user asks a specific question about the process — for example whether a seller can receive dollars when the buyer pays with crypto, how a crypto-backed cash offer or a crypto-funded mortgage down payment works, how to prove they have enough crypto to buy a house, exchange-held crypto, security, timing, taxes, closing, proof of funds, or other product details — returns up to 20 matching entries. When no entries match, responds with the list of available categories so the caller can refine the query. Prefer this over guessing from general 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

NameRequiredDescriptionDefault
queryNoSearch keyword or question to find relevant FAQ entries
categoryNoFilter by FAQ category (e.g. "Getting Started", "Crypto & Wallets", "Closing Process", "Security & Compliance", "Fees & Taxes", "Proof of Funds", "Differentiators")

Output Schema

NameRequiredDescriptionDefault
messageNoDiagnostic message — only present when no entries matched
resultsYesMatching FAQ entries (empty when no entries match)
learn_moreNo
last_updatedNo
result_countNoNumber of matching FAQ entries returned
activation_stageNoFunnel position this response maps to (pre_activation for knowledge answers)
available_categoriesNoAll distinct FAQ categories — returned when no entries matched, so callers can refine the query
recommended_next_actionNoTool 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_labelNoShort CTA label for the suggested next step (e.g. "Verify My Funds")
recommended_next_action_reasonNoWhy 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.

  1. Changed2 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedOutput schema / properties / results / items / additionalProperties
      Previous value: -trueNew value: +{}
  2. Changed4 schema fields changed
    • 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"
+}
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "available_categories": {
+      "description": "All distinct FAQ categories — returned when no entries matched, so callers can refine the query",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "last_updated": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "learn_more": {
+      "type": "string"
+    },
+    "message": {
+      "description": "Diagnostic message — only present when no entries matched",
+      "type": "string"
+    },
+    "result_count": {
+      "description": "Number of matching FAQ entries returned",
+      "type": "number"
+    },
+    "results": {
+      "description": "Matching FAQ entries (empty when no entries match)",
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "answer": {
+            "type": "string"
+          },
+          "category": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "question": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "question",
+          "answer"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "results"
+  ],
+  "type": "object"
+}
  4. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Goes well beyond the read-only/idempotent annotations: it discloses the result cap ('up to 20 matching entries'), the no-match fallback (returns available categories), and detailed next-action metadata semantics including sequencing rules ('never lead with the offer', 'never repeat it after a decline'). This is behavior an agent could not infer from the schema or annotations.

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 and fallback behavior are front-loaded, but the opening sentence is a sprawling example list that could be trimmed, and the next-action metadata passage runs long with repeated prohibitions. Content is mostly justified, yet the density-per-idea is low.

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?

With an output schema present and annotations covering safety, the description fills the remaining gaps: result limit, empty-result behavior, and how to act on next-action metadata. Minor omission: it never states whether search is exact or fuzzy, though that is a small residual gap.

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 coverage is 100% and both parameters are documented there, including category examples. The description only restates 'by keyword and/or category,' which conveys optionality that the schema's empty required list already establishes, so it adds little beyond structured data.

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 and resource ('Search RealOpen's frequently asked questions... by keyword and/or category') with concrete topical scope. It is clearly distinguishable from siblings like get_how_it_works, get_fee_structure, and get_snippets, which cover structured product info rather than free-text FAQ retrieval.

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 an explicit trigger ('when a user asks a specific question about the process') and enumerates the kinds of questions that qualify, plus 'prefer this over guessing from general knowledge.' It stops short of naming which sibling tool to use instead when the question is not an FAQ question (e.g. get_fee_structure for fee tables), so routing is clear but not exhaustive.

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