Skip to main content
Glama

DFX Real Estate Intelligence

by io.github.Capital-W-Holdings
OverviewDiscussionsAdmin

Who could buy, fund or finance this

find_capital_for_opportunity
Read-onlyIdempotent

Investors for a company (dfx_id) or a described opportunity (sector, state, deal size, stage, control): verified independent sponsors with observed acquisitions in the sector (listed, not paired or ranked; company to sponsor pairs are withdrawn), family offices with observed investments or stated sectors in it, venture firms when the opportunity is venture-shaped, and private equity matcher rows where that graph computes them. DFX does not recommend first-time capital providers. Every row says its basis (observed_behaviour, computed_match, observed_investments, derived). 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
stageNo
stateNoTwo-letter US state code.
dfx_idNoA DFX id: dfx:fo:<uuid> (family office graph), dfx:isi:<uuid> (sponsor graph), dfx:vc:<uuid> (venture graph), dfx:pe:<uuid> (private equity graph), dfx:ria:<uuid> (registered investment adviser graph), dfx:al:<uuid> (allocator graph), dfx:pc:<uuid> (private credit graph), dfx:ref:<uuid> (real estate fund graph), or a bare real estate UUID.
sectorNo
controlNo
verticalNo
asset_classNo
deal_size_usdNo
check_size_usdNo
investor_typesNoDefault: independent_sponsor, capital_provider, family_office, venture_capital. private_equity adds the private equity matcher's computed buyers for a company id (always included for a dfx:pe: company).
sponsor_involvedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / dfx_id / description
      Previous value: -"A DFX id: dfx:fo:<uuid> (family office graph), dfx:isi:<uuid> (sponsor graph), dfx:vc:<uuid> (venture graph), dfx:pe:<uuid> (private equity graph), or a bare real estate UUID."New value: +"A DFX id: dfx:fo:<uuid> (family office graph), dfx:isi:<uuid> (sponsor graph), dfx:vc:<uuid> (venture graph), dfx:pe:<uuid> (private equity graph), dfx:ria:<uuid> (registered investment adviser graph), dfx:al:<uuid> (allocator graph), dfx:pc:<uuid> (private credit graph), dfx:ref:<uuid> (real estate fund graph), or a bare real estate UUID."
  2. Changed3 schema fields changed
    • changedInput schema / properties / dfx_id / description
      Previous value: -"A DFX id: dfx:fo:<uuid> (family office graph), dfx:isi:<uuid> (sponsor graph), dfx:vc:<uuid> (venture graph), or a bare real estate UUID."New value: +"A DFX id: dfx:fo:<uuid> (family office graph), dfx:isi:<uuid> (sponsor graph), dfx:vc:<uuid> (venture graph), dfx:pe:<uuid> (private equity graph), or a bare real estate UUID."
    • addedInput schema / properties / investor_types / description
      Added value: +"Default: independent_sponsor, capital_provider, family_office, venture_capital. private_equity adds the private equity matcher's computed buyers for a company id (always included for a dfx:pe: company)."
    • changedInput schema / properties / investor_types / items / enum
      Previous value: -[
-  "independent_sponsor",
-  "capital_provider",
-  "family_office",
-  "venture_capital"
-]New value: +[
+  "independent_sponsor",
+  "capital_provider",
+  "family_office",
+  "venture_capital",
+  "private_equity"
+]
  3. Added

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive), yet the description adds substantial non-obvious behavior: entitlement-gated truncation (first 5 rows plus locked.count/locked.by_type), per-record limits (first 3 related names), hard withholding of contact values and decision-maker names, basis labels on every row, and the entitlement/locked fields in the response. This is exactly the kind of context annotations cannot convey.

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?

Purpose is front-loaded and the sentences are dense with real information about return shape and entitlement. The closing line ('Full access: DFX Intelligence, 7 days free at ...') is promotional filler rather than operational guidance, which slightly dilutes an otherwise tight block.

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?

For a 12-parameter, no-output-schema tool, the description does the heavy lifting: it explains the return shape (basis-labeled rows, entitlement and locked payloads) and the access constraints an agent must anticipate. It falls short only on the handful of unmentioned tuning parameters, which is a modest gap given the complexity covered.

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?

With only 25% schema coverage the description must carry more of the load, and it does explain dfx_id (by describing the company-id mode), sector, state, deal size, stage, and control conceptually. However, it leaves limit, vertical, asset_class, check_size_usd, and sponsor_involved unexplained, so several parameters remain undocumented in both places.

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+resource and enumerates the two input modes (a company dfx_id or a described opportunity via sector/state/deal size/stage/control). It also names the provider categories it returns (independent sponsors, family offices, venture firms, PE matcher rows), which separates it from siblings like find_pe_buyers_for_company and find_vc_investors.

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

Usage Guidelines3/5

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

It gives conditions that select behavior ('venture firms when the opportunity is venture-shaped', 'DFX does not recommend first-time capital providers') and describes the access gating, but never explicitly routes the agent between this tool and near-neighbors such as find_lenders_for_financing, find_opportunities_for_capital, or find_pe_buyers_for_company. Usage is implied rather than stated.

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