Equitest

Find PE and VC fund managers

find_fund_managers

Read-onlyIdempotent

Finds private equity and venture capital firms that report to the US SEC (Form ADV, updated monthly): name, fund type, number of funds, gross assets of their private funds (USD millions), office, website, main office phone, link to the public SEC profile, and whether the firm is already in the user's investor contacts. Firm level only, no personal contacts. Complements find_investors, which uses M&A deals by industry.

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": "find_fund_managers"
  }
}

Input Schema

Name	Required	Description
`limit`	No
`query`	No	Part of the firm name
`state`	No	US state code of the main office, e.g. CA
`country`	No	Country of the main office
`fund_type`	No	Omit for both
`max_fund_assets_mm`	No	USD millions
`min_fund_assets_mm`	No	USD millions

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 7, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, and non-open-world, so the bar is lower. The description adds genuinely useful behavior the annotations cannot: the data source (Form ADV), monthly refresh cadence, and that results are firm-level only with a flag for existing investor contacts.

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 lead clause establishes purpose and data source up front, followed by a compact field list and a sibling comparison. The field enumeration is long but each item (assets in USD millions, SEC profile link, contact flag) tells the agent what it gets, so it largely earns its place.

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?

With seven parameters and no output schema, the description compensates well by spelling out return fields and the data source. Remaining gaps are minor: nothing about the default/max limit of 25/100 or how filters combine, which the schema only partially conveys.

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 description coverage is 86%, so the schema already carries the parameter meanings (state code, USD millions, omit fund_type for both). The description adds no filter or limit guidance of its own, so it does not exceed the baseline for a well-documented 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 names a specific verb and resource (finds PE and VC firms reporting to the SEC) and enumerates the returned data, so an agent knows exactly what the tool yields. It also explicitly distinguishes itself from find_investors by noting that sibling works from M&A deals by industry.

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?

It gives clear context for when this tool is appropriate and routes the agent away from find_investors for the deal-based use case. The 'firm level only, no personal contacts' note implicitly steers toward the contact-oriented siblings, though it never names one explicitly and gives no guidance on combining filters.

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

All Equitest tools Inspect

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

Need Help?