Skip to main content
Glama

People across the family office, sponsor, venture and private equity graphs

search_people
Read-onlyIdempotent

Investment professionals, principals and family office staff as names with titles, roles, seniority, investment responsibility, organisation and tenure, from public filings and firm pages; with domain=ria, IAPD-registered advisors by name or firm. By name, or by organization_dfx_id, or by role. cross_graph_only=true answers 'which venture people are connected to family offices' in one call. organization (a firm name) or organization_dfx_id returns everyone on record at that institution across every graph it is on (one institution is several ids) and every contact source. At least one of query, organization, organization_dfx_id, role, investment_responsibility or cross_graph_only is required; a call with none of them is refused with INVALID_ARGUMENT. Contact points are withheld over MCP; each card whose organisation is on a contact graph carries reachability booleans instead (a verified email or phone on record for that name at that organisation, never the value). 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.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_people"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleNofamily_office: leadership, cio, direct_investments, operations, board, venture, real_estate, family_principal, other. venture_capital: managing_partner, general_partner, partner, principal, vice_president, venture_partner, operating_partner, platform, founder_executive, board, other. private_equity: managing_partner, partner, operating_partner, vice_president, business_development and the other categories on each card.
limitNo
queryNoA person's name (contains). A firm name that matches no person is answered as the firm.
domainNoprivate_credit: officers and control persons of credit managers from their own Form ADV Schedule A. real_estate answers NOT_COVERED: the property graph publishes no people; real estate fund managers' Schedule A people are under real_estate_funds.
current_onlyNo
organizationNoAn organization's NAME (e.g. Akoya Capital Partners): resolved through the identity layer, and everyone on record there is returned from every graph it is on and every contact source, with route types (never values).
prefer_domainNoWith organization: the domain the question is about; it reorders the name's resolution without filtering. Defaults to domain. 'Blackstone' with real_estate_funds reads the real estate advisers' people, not the buyout manager's.
cross_graph_onlyNoOnly people who are the same person on two graphs (a venture professional who is also on a family office's ADV Schedule A), linked by shared individual CRD; returns both cards.
organization_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.
investment_responsibilityNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / prefer_domain
      Added value: +{
      +  "description": "With organization: the domain the question is about; it reorders the name's resolution without filtering. Defaults to domain. 'Blackstone' with real_estate_funds reads the real estate advisers' people, not the buyout manager's.",
      +  "type": "string"
      +}
  2. Changed2 schema fields changed
    • addedInput schema / properties / organization
      Added value: +{
      +  "description": "An organization's NAME (e.g. Akoya Capital Partners): resolved through the identity layer, and everyone on record there is returned from every graph it is on and every contact source, with route types (never values).",
      +  "type": "string"
      +}
    • changedInput schema / properties / query / description
      Previous value: -"A person's name (contains)."New value: +"A person's name (contains). A firm name that matches no person is answered as the firm."
  3. Changed2 schema fields changed
    • addedInput schema / properties / domain / description
      Added value: +"private_credit: officers and control persons of credit managers from their own Form ADV Schedule A. real_estate answers NOT_COVERED: the property graph publishes no people; real estate fund managers' Schedule A people are under real_estate_funds."
    • changedInput schema / properties / domain / enum
      Previous value: -[
      -  "family_office",
      -  "independent_sponsor",
      -  "venture_capital",
      -  "private_equity",
      -  "ria",
      -  "allocators",
      -  "real_estate_funds"
      -]New value: +[
      +  "family_office",
      +  "independent_sponsor",
      +  "venture_capital",
      +  "private_equity",
      +  "ria",
      +  "allocators",
      +  "real_estate_funds",
      +  "private_credit",
      +  "real_estate"
      +]
  4. Changed2 schema fields changed
    • changedInput schema / properties / domain / enum
      Previous value: -[
      -  "family_office",
      -  "independent_sponsor",
      -  "venture_capital",
      -  "private_equity"
      -]New value: +[
      +  "family_office",
      +  "independent_sponsor",
      +  "venture_capital",
      +  "private_equity",
      +  "ria",
      +  "allocators",
      +  "real_estate_funds"
      +]
    • changedInput schema / properties / organization_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."
  5. Changed3 schema fields changed
    • changedInput schema / properties / domain / enum
      Previous value: -[
      -  "family_office",
      -  "independent_sponsor",
      -  "venture_capital"
      -]New value: +[
      +  "family_office",
      +  "independent_sponsor",
      +  "venture_capital",
      +  "private_equity"
      +]
    • changedInput schema / properties / organization_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."
    • changedInput schema / properties / role / description
      Previous value: -"family_office: leadership, cio, direct_investments, operations, board, venture, real_estate, family_principal, other. venture_capital: managing_partner, general_partner, partner, principal, vice_president, venture_partner, operating_partner, platform, founder_executive, board, other."New value: +"family_office: leadership, cio, direct_investments, operations, board, venture, real_estate, family_principal, other. venture_capital: managing_partner, general_partner, partner, principal, vice_president, venture_partner, operating_partner, platform, founder_executive, board, other. private_equity: managing_partner, partner, operating_partner, vice_president, business_development and the other categories on each card."
  6. Changed1 schema field changed
    • addedInput schema / properties / query / description
      Added value: +"A person's name (contains)."
  7. Changed1 schema field changed
    • addedInput schema / properties / cross_graph_only
      Added value: +{
      +  "description": "Only people who are the same person on two graphs (a venture professional who is also on a family office's ADV Schedule A), linked by shared individual CRD; returns both cards.",
      +  "type": "boolean"
      +}
  8. Added

TDQS

A4.1/5.0
Behavior5/5

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

Annotations cover the safety profile (readOnlyHint, idempotentHint, non-destructive), and the description goes well beyond them: contact values are withheld over MCP with `reachability` booleans substituted, decision-maker names are never returned, unentitled calls return only 5 rows plus locked.count/locked.by_type, and every answer reports `entitlement` and `locked`. This is exactly the kind of auth-gating and data-withholding context an agent needs before calling.

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 largely substantive, but it is delivered as one long undifferentiated block mixing purpose, parameter behavior, entitlement limits and a closing promotional line ('7 days free at https://dfxintel.com/data-factory/plans'), which does not earn its place. Front-loading is good, but structure and readability suffer.

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 10-parameter tool with no output schema, the description covers a great deal: entitlement behavior, the locked/entitlement response fields, contact withholding and the required-parameter rule. It still leaves limit, current_only and pagination/ordering semantics unexplained, so it is strong but not exhaustive.

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 coverage is 70% and the schema itself documents role enums, domain variants, prefer_domain, cross_graph_only and organization_dfx_id well. The description adds real value on combination semantics ('one institution is several ids', organization returns everyone across every graph, the at-least-one-parameter rule), but says nothing about limit, current_only or result ordering.

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 names the specific resource (investment professionals, principals, family office staff with titles, roles, seniority, tenure) and the sources (public filings, firm pages), plus the domain=ria variant for IAPD-registered advisors. It is clearly a people-search tool rather than a firm search, though it never explicitly names the sibling tools (search_family_offices, search_ria, search_allocators) it should be preferred over.

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?

Strong explicit gating: 'At least one of query, organization, organization_dfx_id, role, investment_responsibility or cross_graph_only is required; a call with none of them is refused with INVALID_ARGUMENT,' and it states the three primary lookup modes (by name, by organization_dfx_id, by role). It lacks explicit routing to alternatives (e.g., when to use a firm-level search instead), which keeps it short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.