Skip to main content
Glama

DFX Real Estate Intelligence

by io.github.Capital-W-Holdings
OverviewDiscussionsAdmin

One RIA firm in full

get_ria_firm
Read-onlyIdempotent

The full card for one registered investment adviser plus its people flows (joins, departures, net, rates over 90 days, 12 and 36 months), growth between annual amendments (RAUM, employees, offices, funds one and three years back), offices (city, state, postal, employees), owners with control persons first (Schedule A and B), affiliates (Item 7.A related persons with roles), its ten largest private funds with the count still reported, teams that left or arrived, the latest departures and arrivals, recent events, and same_as links to the private equity, venture, family office and sponsor graphs by shared CRD, CIK or fund id. Every section is a page with its size stated. Every row names its fact class (reported: filed on Form ADV; fact_from_registration: IAPD registration dates; derived: a rule or arithmetic over filed inputs). RAUM double counts affiliates; no advisor book size exists or is estimated; the IAPD tape is survivor-biased before 2026-09-15. Nothing here is predictive. Accepts dfx:ria: ids or a CRD. 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
dfx_idYesAn RIA graph id of the form dfx:ria:<uuid> (from search_ria, resolve_name or search_entities), or the firm's CRD number as a string.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the read-only/idempotent/non-destructive profile, and the description adds substantial context beyond them: entitlement gating (first 5 rows, locked.count/locked.by_type, withheld contact values), data provenance classes (reported/fact_from_registration/derived), RAUM affiliate double counting, and survivor bias before 2026-09-15. These are genuinely useful caveats, though the framing is marketing-tinged.

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 content is dense and mostly earns its place, but it is delivered as one undifferentiated paragraph, and the closing sales pitch ('7 days free at https://dfxintel.com/...') is promotional rather than functional. A sectioned layout would serve the reader better.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description carries the full burden and does so: it enumerates returned sections, explains pagination/entitlement behavior and locked structures, defines fact classes, and notes data-quality caveats. An agent knows what it will get and what may be withheld.

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 the single parameter's id format (dfx:ria:<uuid> or CRD) is already documented in the schema. The description repeats the same id acceptance without adding syntax or resolution behavior, so it meets the baseline but does not exceed it.

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 (get one RIA firm's full card) and enumerates the exact sections returned: people flows, growth, offices, owners, affiliates, funds, teams, events, same_as links. That enumeration distinguishes it from siblings like get_ria_advisor, get_ria_practice and get_ria_trends without ambiguity.

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 specifies accepted identifiers ('dfx:ria: ids or a CRD') and implies this is the full-record counterpart to list/search tools, but it never states when to choose this over get_ria_advisor or search_ria, nor any exclusion conditions. Usage is inferable rather than explicit.

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