Skip to main content
Glama

DFX Real Estate Intelligence

by io.github.Capital-W-Holdings
OverviewDiscussionsAdmin

Search independent sponsors

search_independent_sponsors
Read-onlyIdempotent

Verified independent sponsor firms (deal-by-deal acquirers of lower middle market companies) as compact cards: verification status, classification, mandate summary, principals, vehicle count and latest vehicle, and how many companies resemble the sponsor's observed deals. Only firms whose identity evidence names them (eligibility VERIFIED_SPONSOR_FIRM) are returned unless include_unverified is true, which returns the unverified filing groups and candidates as a labelled research list. With sector, the answer is OBSERVED behaviour: verified sponsors with observed deals in that vertical first. Returns dfx:isi: ids. Capital providers and target companies are not in these results.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cityNo
kindNo
sortNo
limitNo
queryNo
stateNoTwo-letter US state code.
sectorNoFree text mapped onto the eight verticals (business_services, industrial_manufacturing, industrial_services, healthcare_services, consumer_services, specialty_distribution, transportation_logistics, tech_enabled_services); text that maps to none is matched against the mandate summary.
min_confidenceNo
include_unverifiedNotrue returns the research list instead: unverified Form D filing groups and candidates, never paired with companies. Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / include_unverified
      Added value: +{
+  "description": "true returns the research list instead: unverified Form D filing groups and candidates, never paired with companies. Default false.",
+  "type": "boolean"
+}
  2. Added

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the description doesn't need to repeat safety. However, it adds behavioral context about the output format (compact cards, labelled research list), how unverified firms are handled, and the special behavior with 'sector' (observed deals first). It doesn't disclose potential latency or pagination, but the extra context justifies a 3.

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

Conciseness4/5

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

The description is dense but not overly long. It front-loads the core purpose and output format, then covers edge cases. The sentences are packed with information, but every part is relevant. Minor redundancy with annotations (readOnly) but no waste.

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 search tool with no output schema, the description gives a rich picture of what is returned: fields like verification status, classification, mandate summary, principals, vehicle count, and similarity counts. It also explains the behavior with unverified and sector. The remaining gap is not explaining the 'sort' parameter's effect on relevance, but overall it is complete enough for an agent.

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 only 33%, so the description carries extra weight. It explains the meaning of the 'sector' parameter (maps to eight verticals, falls back to mandate summary), 'include_unverified' (returns research list), and 'kind' (though not fully detailed). This adds significant value beyond the bare schema.

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?

The description clearly states the tool searches for verified independent sponsor firms, with a specific resource type and scope. It distinguishes itself from siblings by explicitly excluding capital providers and target companies, and by mentioning the 'dfx:isi:' id prefix, which helps differentiate from other entity-related tools.

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?

The description explains when to use the tool: for verified sponsors, and when to use the research list (with include_unverified). It also clarifies that capital providers and target companies are not included, which prevents misuse. However, it doesn't explicitly name alternatives like get_independent_sponsor or search_sponsor_deals for more specific queries.

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