Skip to main content
Glama

Prilago Institutional LP & GP Fundraising Intelligence

search_lps

Search Prilago's 5,262 direct institutional LPs (Private Foundations, Public & Corporate Pensions, University Endowments, Healthcare Systems, Insurers, Institutional Trusts, and Sovereign Funds) by name, institution type, geography, strategy, or retained investment consultant.

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_lps"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum LPs to return (1 to 40, default 15).
queryNoInvestor name, city/state, or keyword (e.g. 'Surdna Foundation', 'UTIMCO', 'California', 'WSIB').
lp_typeNoOptional institution type filter: 'Private Foundation', 'Public Pension Plan', 'Corporate Pension', 'University Endowment', 'Healthcare / Hospital System', 'Insurance Company', 'Institutional Trust', or 'Sovereign Wealth Fund'.
strategyNoOptional fund strategy filter (e.g. 'Venture Capital', 'Buyout', 'Growth Equity', 'Direct Lending', 'Real Estate').
consultantNoOptional retained investment consultant filter (e.g. 'Aksia', 'Meketa', 'Hamilton Lane', 'Cambridge Associates', 'NEPC').

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / lp_type / description
      Previous value: -"Optional allocator segment filter: 'Public Pension Plan', 'Private Foundation', 'Family Office / MFO', 'OCIO / Wealth RIA', 'Fund of Funds / Seeder', 'University Endowment', 'Insurance Company', or 'Sovereign Wealth Fund'."New value: +"Optional institution type filter: 'Private Foundation', 'Public Pension Plan', 'Corporate Pension', 'University Endowment', 'Healthcare / Hospital System', 'Insurance Company', 'Institutional Trust', or 'Sovereign Wealth Fund'."
    • changedInput schema / properties / query / description
      Previous value: -"LP name, city/state, or keyword (e.g. 'Ford Foundation', 'California', 'Family Office', 'CalPERS')."New value: +"Investor name, city/state, or keyword (e.g. 'Surdna Foundation', 'UTIMCO', 'California', 'WSIB')."
    • changedInput schema / properties / strategy / description
      Previous value: -"Optional fund strategy filter (e.g. 'Healthcare Buyout', 'Venture Capital', 'Private Credit', 'Lower Middle Market')."New value: +"Optional fund strategy filter (e.g. 'Venture Capital', 'Buyout', 'Growth Equity', 'Direct Lending', 'Real Estate')."
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries full behavioral burden. 'Search' implies a safe read, and the corpus size (5,262) gives useful scale context, but it does not state whether an empty query returns everything, how results are ordered, whether pagination exists beyond the limit cap, or what the coverage/currency of the dataset is.

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?

A single front-loaded sentence that leads with the verb, scope, and corpus size before the filter list. The parenthetical enumeration of all seven LP types is slightly long but carries genuine informational value, so little is wasted.

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 five-parameter, no-required-parameter search tool with no output schema and no annotations, the description should say more about what a result record contains and how partial matches are scored. It adequately covers the input side but leaves return shape and empty-query behavior unaddressed.

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 the schema already documents all five parameters with examples and allowed values. The description adds only a conceptual mapping of filters (notably that geography is searched through the query parameter) and otherwise restates what the schema provides, so baseline 3 applies.

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 ('Search') applied to a precisely scoped resource ('Prilago's 5,262 direct institutional LPs'), then enumerates the dimensions that can be searched. An agent knows immediately this is a filtered LP lookup, distinct from siblings like get_lp_360_dossier or match_fund_to_lps.

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?

The list of searchable dimensions implies when to reach for this tool (name, type, geography, strategy, consultant), but there is no explicit when-to-use guidance, no exclusions, and no mention of the sibling tools that retrieve LP detail or perform matching. Usage is inferable rather than stated.

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