Skip to main content
Glama

Prilago Institutional LP & GP Fundraising Intelligence

get_gp_peer_lookalikes

Inspect any General Partner (Fund Manager) from verified LP disclosures: lists direct institutional LPs backing their funds, repeat re-up LPs, median disclosed check size, filed Net IRR / TVPI / DPI, and peer GPs.

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": {
      "gp_name": "<gp_name>"
    },
    "name": "get_gp_peer_lookalikes"
  }
}

Input Schema

NameRequiredDescriptionDefault
gp_nameYesBenchmark or peer GP firm name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / gp_name / description
      Previous value: -"Competitor or benchmark GP firm name (e.g. 'Thoma Bravo', 'Frazier Healthcare Partners', 'Alpine Investors', 'KKR', 'Ares')."New value: +"Benchmark or peer GP firm name."
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations at all, the description carries the full behavioral burden. It usefully discloses data provenance ('verified LP disclosures') and the breadth of returned fields, which implies a read-only inspection tool. However, it says nothing about what happens when a GP name is ambiguous or unmatched, how coverage varies across GPs, or whether the financial metrics are always present.

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 immediately identifies the subject and then lists the payload. No filler or repetition; the only weakness is that the colon-separated field list does a lot of work without any structural separation between lookup behavior and return contents.

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 one-parameter read tool with no output schema and no annotations, the description compensates well by enumerating the return fields, effectively standing in for the missing output schema. What remains missing is edge-case behavior (ambiguous or unknown GP names) and the absence of any safety or auth context.

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?

Only one parameter exists and schema coverage is 100%, so gp_name is already documented as 'Benchmark or peer GP firm name'. The description adds mild value by clarifying the entity type as a General Partner / Fund Manager rather than an LP, but it gives no guidance on name format, aliases, or matching tolerance.

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 a specific verb ('Inspect') and resource ('any General Partner (Fund Manager)') and enumerates the exact content returned: backing institutional LPs, re-up LPs, median check size, Net IRR/TVPI/DPI, and peer GPs. It is clearly a GP-level lookup rather than an LP search, but it never names or contrasts the adjacent tools such as get_lp_360_dossier or match_fund_to_lps, so the distinction has to be inferred.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance. 'Inspect any General Partner' implies a lookup, but the description never says which situations call for this tool versus the sibling LP-oriented or matching tools, nor are any prerequisites (e.g., whether the GP name must be exact) 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