Skip to main content
Glama

Prilago Institutional LP & GP Fundraising Intelligence

match_fund_to_lps

Find direct institutional LPs proven in primary filings to back early-series funds (Funds I to IV) from managers under $5B AUM in your strategy and check-size band, automatically removing any existing investors of a reference manager. Uses the exact same Early-Backers ranking engine as the Prilago web app.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "strategy": "<strategy>"
    },
    "name": "match_fund_to_lps"
  }
}

Input Schema

NameRequiredDescriptionDefault
top_nNoNumber of top ranked LPs to return (1 to 50, default 25).
strategyYesFund strategy or family ('Venture Capital', 'Buyout', 'Growth Equity', 'Direct Lending', 'Real Estate', 'Infrastructure').
fund_nameNoGP's fund name (e.g. 'Apex Partners II').Fund II
fund_size_mmNoTarget fund size in $ Millions (e.g. 75).
max_check_mmNoTarget / reference LP check size in $ Millions (e.g. 5).
min_check_mmNoMinimum LP check size in $ Millions (e.g. 0.25).
region_focusNoOptional location/region filter (e.g. 'All', 'CA', 'NY', 'Northeast', 'Pacific').All
manager_queryNoOptional reference or peer manager name to exclude existing LPs and weight shared peers.
fund_generationNo'first_time' (Fund I), 'emerging' (Funds I to IV), or 'established' (Fund V+ allocation fit).emerging
allocator_segmentNoOptional institution type filter (e.g. 'All', 'Private Foundation', 'University Endowment', 'Public Pension Plan').All

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed14 schema fields changed
    • changedInput schema / properties / allocator_segment / description
      Previous value: -"Optional segment focus: 'All', 'fund_1_3_friendly' (Foundations, MFOs, OCIOs, FoF Seeders & Endowments), 'Private Foundation', 'Family Office / MFO', 'OCIO / Wealth RIA', 'Fund of Funds / Seeder', 'Insurance Company', or 'Public Pension Plan'."New value: +"Optional institution type filter (e.g. 'All', 'Private Foundation', 'University Endowment', 'Public Pension Plan')."
    • changedInput schema / properties / fund_generation / description
      Previous value: -"'first_time' (Fund I), 'emerging' (Fund II–III), or 'established' (Fund IV+)."New value: +"'first_time' (Fund I), 'emerging' (Funds I to IV), or 'established' (Fund V+ allocation fit)."
    • changedInput schema / properties / fund_name / description
      Previous value: -"GP's fund name (e.g. 'Apex Healthcare Partners II')."New value: +"GP's fund name (e.g. 'Apex Partners II')."
    • changedInput schema / properties / fund_size_mm / default
      Previous value: -200New value: +75
    • changedInput schema / properties / fund_size_mm / description
      Previous value: -"Target total fund size in $ Millions (e.g. 250)."New value: +"Target fund size in $ Millions (e.g. 75)."
    • addedInput schema / properties / manager_query
      Added value: +{
      +  "description": "Optional reference or peer manager name to exclude existing LPs and weight shared peers.",
      +  "type": "string"
      +}
    • changedInput schema / properties / max_check_mm / default
      Previous value: -30New value: +5
    • changedInput schema / properties / max_check_mm / description
      Previous value: -"Maximum target LP check size in $ Millions (e.g. 30)."New value: +"Target / reference LP check size in $ Millions (e.g. 5)."
    • changedInput schema / properties / min_check_mm / default
      Previous value: -5New value: +0.25
    • changedInput schema / properties / min_check_mm / description
      Previous value: -"Minimum target LP check size in $ Millions (e.g. 5)."New value: +"Minimum LP check size in $ Millions (e.g. 0.25)."
    • changedInput schema / properties / region_focus / description
      Previous value: -"Optional LP region filter: 'All', 'North America', 'Europe', or 'Asia'."New value: +"Optional location/region filter (e.g. 'All', 'CA', 'NY', 'Northeast', 'Pacific')."
    • changedInput schema / properties / strategy / description
      Previous value: -"Exact fund strategy & sector thesis (e.g. 'Healthcare Buyout', 'B2B AI Seed Venture', 'Direct Lending Private Credit')."New value: +"Fund strategy or family ('Venture Capital', 'Buyout', 'Growth Equity', 'Direct Lending', 'Real Estate', 'Infrastructure')."
    • changedInput schema / properties / top_n / default
      Previous value: -20New value: +25
    • changedInput schema / properties / top_n / description
      Previous value: -"Number of top ranked LPs to return (1 to 35, default 20)."New value: +"Number of top ranked LPs to return (1 to 50, default 25)."
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose non-schema behavior: results come from primary filings, existing investors of a reference manager are automatically removed, shared peers are weighted, and the ranking engine is the same as the web app. It lacks any statement about read-only safety, result volume limits beyond top_n, or pagination, and the fixed 'Funds I to IV' framing sits awkwardly against fund_generation options for first_time and established.

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?

Two front-loaded sentences with the search scope first and the engine-provenance note second; little waste. The web-app parity sentence is partly promotional but does convey ranking provenance, so it earns its place marginally.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 and no annotations, the description covers the sourcing premise and the exclusion behavior but never characterizes the returned ranked list (fields, scores, caveats) that an agent needs to interpret results. The mismatch between the description's fixed 'Funds I to IV' scope and the fund_generation enum also leaves an ambiguity unresolved.

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 100%, so parameter meaning is already fully documented, and the description adds little beyond restating strategy and check-size band. It also introduces a fixed 'under $5B AUM' manager constraint that has no corresponding parameter, which could mislead an agent about how manager_query and fund_generation interact.

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 and resource ('Find direct institutional LPs') plus distinctive scope: primary-filing-verified, early-series funds (I–IV), managers under $5B AUM, strategy and check-size band, with automatic removal of a reference manager's existing investors. That is materially different from siblings like search_lps or get_lp_360_dossier, so an agent can route correctly without opening another schema.

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

Usage Guidelines3/5

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

Usage is implied by the framing ('proven in primary filings to back early-series funds') and by the exclusion behavior triggered by manager_query, so an agent can guess this is a ranked sourcing tool rather than a generic LP lookup. However, there is no explicit when-to-use statement, no when-not, and no named alternative to search_lps for plain LP queries.

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.

Resources