Skip to main content
Glama

DFX Real Estate Intelligence

by io.github.Capital-W-Holdings
OverviewDiscussionsAdmin

Opportunities built from signals

search_opportunities
Read-onlyIdempotent

Opportunity summaries: the condition (credit deterioration, refinancing window, lender group change, capital raised, advisor movement, servicing distress ...), the subject with its dfx id, the signal families and published signals behind it, first and last observed dates, exposure with basis, the intelligence class (JOINED, INFERRED, DERIVED, DFX_EXCLUSIVE ...), beneficiary classes, and COUNTS of named and reachable beneficiaries. No contacts and no sales state. Filter by condition, class, subject id or minimum rank. ACCESS: without a paid DFX plan on the vertical, a list returns its first 5 rows in full and a count of the rest by type (locked.count, locked.by_type), never the rows; a record names its subject and the first 3 related names per section; contact values (email, phone, profile URLs) and decision-maker names are never returned, only their types and counts. Every answer says what it withheld in entitlement and locked. Full access: DFX Intelligence, 7 days free at https://dfxintel.com/data-factory/plans.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
queryNoSubject name contains.
cursorNonext_cursor from a previous page of this tool, unchanged.
familyNoA signal family the opportunity carries.
min_rankNo
include_heldNoAlso return private credit opportunities the shared contract HOLDS (a family that has not passed blind truth checks), each with its hold reason. Default: left out.
condition_kindNo
subject_dfx_idNoA DFX id (dfx:<graph>:<uuid>) or a bare real estate UUID.
intelligence_classNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / include_held
      Added value: +{
+  "default": false,
+  "description": "Also return private credit opportunities the shared contract HOLDS (a family that has not passed blind truth checks), each with its hold reason. Default: left out.",
+  "type": "boolean"
+}
  2. Added

TDQS

A3.7/5.0
Behavior5/5

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

Annotations cover safety (readOnly, idempotent, non-destructive). Description adds substantial context beyond annotations: entitlement/locked behavior, withholding of contact values and decision-maker names, first-5-rows limit for unpaid plans, and what is reported in entitlement and locked fields. No contradiction.

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?

Front-loads the returned fields, then filters, then access rules. Structure is logical. Includes some redundancy ('No contacts and no sales state' vs later contact values never returned) and a promotional URL, but the length is justified by complex access rules.

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?

Given no output schema, the description adequately describes return fields and access behavior. It covers filters and withholding. Missing detailed parameter semantics for some fields, but annotations and schema cover safety and some params. Complete enough for invocation.

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 56%. Description names filter fields (condition, class, subject id, min rank) and lists condition kinds and intelligence classes, adding meaning to those enums. However, it does not cover limit, cursor, include_held, query, or family beyond schema descriptions. Partial compensation for coverage gap.

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

Purpose4/5

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

Describes a specific resource (opportunity summaries) and enumerates the fields returned, including condition types, intelligence class, and beneficiary counts. Distinguishes from contact/sales data by stating 'No contacts and no sales state.' Does not explicitly differentiate from sibling opportunity-search tools (e.g., search_forward_opportunities, search_vc_opportunities), so not a 5.

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

Usage Guidelines2/5

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

Provides filter options (condition, class, subject id, min rank) but no when-to-use guidance or alternatives among the many sibling opportunity-search tools. Access rules indicate context but not selection criteria.

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

All DFX Real Estate Intelligence 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