Skip to main content
Glama

DFX Real Estate Intelligence

by io.github.Capital-W-Holdings
OverviewDiscussionsAdmin

RIA acquisitions and exits as filed facts

search_ria_ma
Read-onlyIdempotent

RIA M&A from three factual sources, each labelled: successions the acquirer swore on Form ADV Item 4 (succession); firms whose advisors re-registered whole at one other firm (absorbed, a rule over registration dates); and firms that left the SEC adviser roster (roster_exit; the reason is not stated). Each row carries the target and, where there is one, the acquirer as dfx:ria: ids, the date, headline, advisor count or RAUM as magnitude, and the source. Filter by kind, acquirer or target CRD, firm id, date window or minimum advisors. Absorbed also returns acquisitions measured from registration history (a succession, half the firm in one 14-day chain, or 25 or more advisors in one month) with the advisors transferred, how many are still registered through the acquirer at 30, 90, 182 and 365 days, and the pooled retention of similar-size deals. No press, no rumours, no predictions. 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
kindNoall
limitNo
sinceNoISO date.
untilNo
cursorNonext_cursor from a previous page of this tool, unchanged.
targetNoThe acquired firm's name; every adviser CRD carrying it (whole words) is included.
acquirerNoThe acquirer's name; every adviser CRD carrying it (whole words) is included.
target_crdNo
firm_dfx_idNoA dfx:ria: firm id or CRD on either side of the event.
acquirer_crdNo
min_advisorsNoAbsorbed only: at least this many advisors moved.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / acquirer
      Added value: +{
+  "description": "The acquirer's name; every adviser CRD carrying it (whole words) is included.",
+  "type": "string"
+}
    • addedInput schema / properties / target
      Added value: +{
+  "description": "The acquired firm's name; every adviser CRD carrying it (whole words) is included.",
+  "type": "string"
+}
  2. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations cover safety (readOnly, idempotent, non-destructive) and the description adds substantial behavior beyond them: entitlement-gated returns, the 5-row cap with locked.count/locked.by_type, redaction of contact values and decision-maker names, and the `entitlement`/`locked` withholding fields. This is exactly the kind of access/return behavior an agent needs and cannot get from 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 core facts are front-loaded and dense, appropriate for a complex 11-parameter tool, but the closing sales pitch ('Full access: DFX Intelligence, 7 days free at https://dfxintel.com/...') does not help an agent select or invoke the tool and the run-on sentences reduce scannability.

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?

Despite no output schema and 11 params, the description explains what each row carries (target/acquirer dfx:ria: ids, date, headline, advisor count or RAUM, source), what the absorbed kind additionally returns (transfer counts, retention at 30/90/182/365 days, pooled retention), and how entitlement alters results. An agent has enough to call it and interpret results.

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?

With 55% schema coverage and 11 params, the description compensates by naming the filter dimensions (kind, acquirer/target CRD, firm id, date window, minimum advisors) and scoping min_advisors to 'Absorbed only'. It adds meaning beyond the schema but does not fully document every parameter (e.g. cursor semantics, target vs acquirer name matching).

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 resource (RIA M&A) and enumerates the three distinct factual kinds (succession, absorbed, roster_exit) with what each means, so an agent can tell it apart from siblings like search_ria_changes or search_ria_advisor_moves. It also explicitly delimits scope with 'No press, no rumours, no predictions.'

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 clear context for when this applies (filed M&A facts, three source types) and an exclusion ('no press, no rumours, no predictions'), plus field-level scoping like 'Absorbed only' for min_advisors. It does not name a competing sibling tool or say when to prefer an alternative, so it stops short of the 5 bar.

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