DFX Real Estate Intelligence

Search real estate fund managers

search_re_fund_managers

Read-onlyIdempotent

Advisers that swear a Real Estate Fund vehicle on Form ADV Schedule D 7.B.(1): one manager is one CRD, with its registration and latest filing, regulatory assets under management, the summed gross asset value of its non-feeder, non-quarantined real estate vehicles with its size band, vehicles current and ever, strategy class with its state and basis, operator model, property types and markets with their bases, validated property bindings and their loans, and the public plans that disclose commitments. Filter by state (the manager's headquarters), strategy class, size band, operator model, gross asset value, vehicles, property type, holdings or public LPs, and by ACTIVITY on its validated holdings: acquisitions or financings in the last 12 months, a loan maturing before a date, the latest vintage, the year of its first real estate vehicle (emerging managers). similar_to gives the managers with the same strategy class and a shared property type, the subject excluded. Sort by gav, acquisitions, financings, maturity, vintage, newest, loans, lps, recent. Every row carries its activity numbers. Gross asset value is a fund's assets on a filing date: never fund size, never commitments, never dry powder, and a quarantined reading enters no sum. The sworn ADV tape starts in 2011 and runs through the latest monthly filings DFX has read (coverage_live on the answer gives the years and counts), so a first report in 2011 or 2012 is a first sighting, not a formation. Holdings, properties, loans and lenders appear only where a property binding passed its blind labels, which is a few hundred managers. 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

Name	Required	Description
`crd`	No
`sort`	No
`limit`	No
`query`	No	Manager name contains, or a CRD.
`state`	No	Two-letter US state code.
`cursor`	No	next_cursor from a previous page of this tool, unchanged.
`size_band`	No
`similar_to`	No	A real estate fund manager: a dfx:ref:<uuid> id or the manager's CRD.
`with_loans`	No	Only managers with at least one loan on a validated holding.
`max_gav_usd`	No
`min_gav_usd`	No
`min_vehicles`	No
`property_type`	No	A property type on the manager's own list: MULTIFAMILY, INDUSTRIAL, OFFICE, RETAIL, HOTEL, MIXED_USE, LAND, STUDENT_HOUSING, SENIOR_HOUSING, SELF_STORAGE, SINGLE_FAMILY_RENTAL, DATA_CENTER, HEALTHCARE, LIFE_SCIENCE, MANUFACTURED_HOUSING, NET_LEASE, OTHER (words such as 'apartments' or 'data centers' are folded).
`with_holdings`	No	Only managers with at least one validated property binding.
`include_former`	No	Also managers whose latest filing no longer swears a real estate fund.
`operator_model`	No
`strategy_class`	No	VALUE_ADD, CORE, OPPORTUNISTIC, DEBT... (a word such as 'value add' is folded to the vocabulary).
`maturing_before`	No	ISO date: the manager's next loan maturity falls between today and this date.
`with_public_lps`	No
`min_financings_12m`	No
`latest_vintage_from`	No	Its newest vehicle's vintage is this year or later.
`min_acquisitions_12m`	No	Acquisitions recorded at its validated holdings in the last 12 months, at least this many (1 = actively acquiring).
`first_vehicle_year_from`	No	Its first real estate vehicle on the tape is this year or later (emerging managers; the tape starts 2011).

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 schema fields changedOct 6, 2026

addedInput schema / properties / first_vehicle_year_from

Added value: +{
+  "description": "Its first real estate vehicle on the tape is this year or later (emerging managers; the tape starts 2011).",
+  "type": "integer"
+}

addedInput schema / properties / latest_vintage_from

Added value: +{
+  "description": "Its newest vehicle's vintage is this year or later.",
+  "type": "integer"
+}

addedInput schema / properties / maturing_before

Added value: +{
+  "description": "ISO date: the manager's next loan maturity falls between today and this date.",
+  "type": "string"
+}

addedInput schema / properties / min_acquisitions_12m

Added value: +{
+  "description": "Acquisitions recorded at its validated holdings in the last 12 months, at least this many (1 = actively acquiring).",
+  "type": "integer"
+}

addedInput schema / properties / min_financings_12m
```
Added value: +{
+  "type": "integer"
+}
```

changedInput schema / properties / property_type / description

Previous value: -"A property type on the manager's own list (MULTIFAMILY, INDUSTRIAL, OFFICE, RETAIL, ...)."New value: +"A property type on the manager's own list: MULTIFAMILY, INDUSTRIAL, OFFICE, RETAIL, HOTEL, MIXED_USE, LAND, STUDENT_HOUSING, SENIOR_HOUSING, SELF_STORAGE, SINGLE_FAMILY_RENTAL, DATA_CENTER, HEALTHCARE, LIFE_SCIENCE, MANUFACTURED_HOUSING, NET_LEASE, OTHER (words such as 'apartments' or 'data centers' are folded)."

addedInput schema / properties / similar_to

Added value: +{
+  "description": "A real estate fund manager: a dfx:ref:<uuid> id or the manager's CRD.",
+  "type": "string"
+}

changedInput schema / properties / sort / enum

Previous value: -[
-  "gav",
-  "vehicles",
-  "raum",
-  "lps",
-  "recent",
-  "name"
-]New value: +[
+  "acquisitions",
+  "financings",
+  "gav",
+  "loans",
+  "lps",
+  "maturity",
+  "name",
+  "newest",
+  "raum",
+  "recent",
+  "vehicles",
+  "vintage"
+]

addedInput schema / properties / strategy_class / description

Added value: +"VALUE_ADD, CORE, OPPORTUNISTIC, DEBT... (a word such as 'value add' is folded to the vocabulary)."

addedInput schema / properties / with_loans

Added value: +{
+  "description": "Only managers with at least one loan on a validated holding.",
+  "type": "boolean"
+}

AddedSep 18, 2026

TDQS

A3.8/5.0

Behavior5/5

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

Annotations already cover safety and idempotency, but the description adds substantial behavioral context: entitlement limits (first 5 rows only without a paid plan, locked counts by type), what is never returned (contact values, decision-maker names), how withheld data is reported in `entitlement` and `locked`, the 2011 start of the sworn ADV tape, and the fact that holdings only appear when a property binding passed blind labels.

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

Conciseness2/5

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

The description is a single, dense, run-on paragraph of over 250 words with no bullet points or clear front-loading. Valuable information is buried in long clauses, making it hard for an agent to parse quickly. It is over-specified rather than concise.

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 23-parameter search tool with no output schema, the description is largely complete: it explains what each row carries, how filtering and sorting work, the meaning of GAV, access restrictions, and coverage caveats. It omits some parameter details and pagination behavior, but the structured schema covers cursor and limits.

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?

Schema description coverage is moderate (57%) with 23 parameters. The description compensates by defining gross asset value (never fund size, commitments, or dry powder), clarifying that state means headquarters, explaining similar_to's behavior (same strategy class and shared property type, subject excluded), and describing activity filters like acquisitions, financings, and maturities. It does not cover every parameter (e.g., limit, cursor, min_vehicles), but adds meaningful semantics beyond the schema for several key filters.

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?

The description identifies the exact resource: advisers that swear a Real Estate Fund vehicle on Form ADV Schedule D 7.B.(1), with one manager equaling one CRD. This is a clear and specific entity, though it never explicitly distinguishes this tool from siblings like search_re_fund_vehicles or get_re_fund_manager.

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 lists many filters and sort options, and explains what similar_to does, so usage is implied. However, it never states when to choose this tool over the many sibling search tools, nor does it set exclusions or prerequisites beyond the filter mechanics.

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 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.

Search real estate fund managers

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources