Skip to main content
Glama

DFX Real Estate Intelligence

by io.github.Capital-W-Holdings
OverviewDiscussionsAdmin

A name to DFX ids, fast, across every private capital graph

resolve_name
Read-onlyIdempotent

Resolve a firm, fund, person or company name to canonical dfx ids from the Data Factory's index of every published name and alias (former names, dbas, legal names) on the family office, sponsor, venture, private equity, RIA, allocator, private credit and real estate fund graphs as each graph is indexed. Each row carries the ROLES the institution holds across graphs where the identity layer publishes them, so one institution that is a private equity manager, a registered adviser, a private credit manager, a real estate fund manager and a manager holding allocator capital comes back as one identity with the id on each graph, never as five unrelated firms. Ranked exact, prefix, then word match; one row per entity; typically under 200 ms. The first call before get_entity. Real estate organisations are resolved by resolve_organization instead. 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
nameYesThe name, or a word of it (Blackstone, Horowitz, Thoma).
limitNo
domainNoComma-separated: family_office, independent_sponsor, venture_capital, private_equity, ria, allocators, private_credit, real_estate_funds. Default: all.
entity_typeNoComma-separated graph types: organization, office, sponsor, capital_provider, fund, person, company.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / domain / description
      Previous value: -"Comma-separated: family_office, independent_sponsor, venture_capital, private_equity. Default: all four."New value: +"Comma-separated: family_office, independent_sponsor, venture_capital, private_equity, ria, allocators, private_credit, real_estate_funds. Default: all."
  2. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, yet the description adds substantial behavioral context beyond them: match ranking (exact, prefix, word), one-row-per-entity de-duplication, typical latency under 200ms, and a detailed entitlement model (5 rows + counts when locked, contact values withheld, entitlement/locked fields). The remaining gap is that the `locked`/`entitlement` return shape is asserted but not illustrated.

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 behavior is front-loaded and dense, but the run-on identity sentence is hard to parse and the closing 'DFX Intelligence, 7 days free at https://...' line is promotional rather than operational, padding the definition.

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?

For a read-only lookup with no output schema, the description covers matching semantics, cardinality (one row per entity), roles, latency, and the full access/withholding model. An agent has everything needed to call it and interpret a truncated response.

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 75% schema coverage the baseline is already 3, and the description adds real meaning: `name` matches aliases/former names/dbas/legal names and accepts a partial word, `domain` enumerates the graph verticals, and the role-merging behavior explains why one entity may surface across graphs. Only `limit` goes unaddressed.

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 ('Resolve a ... name to canonical dfx ids') and pins the scope to the Data Factory name/alias index across named graph verticals. It also pre-empts confusion with the nearest sibling by stating real estate organisations are resolved by resolve_organization instead.

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

Usage Guidelines5/5

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

Explicitly positions itself as 'the first call before get_entity' and routes a competing case (real estate organisations) to resolve_organization. That is a clear when-to-use plus an exclusion with a named alternative.

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