Skip to main content
Glama

Prilago Institutional LP & GP Fundraising Intelligence

get_lp_360_dossier

Retrieve the complete Prilago Investor Profile for a specific Limited Partner: Total AUM, Target vs. Actual Private Equity / Credit / Real Assets room under target ($M), disclosed pacing plan, retained investment consultants, named investment-staff and governance contacts, filed Net IRR / TVPI / DPI figures, repeat GP relationships, primary-sourced fund holdings, and filing signals.

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": {
      "lp_name": "<lp_name>"
    },
    "name": "get_lp_360_dossier"
  }
}

Input Schema

NameRequiredDescriptionDefault
lp_nameYesInvestor name or common acronym (e.g. 'Surdna Foundation', 'UTIMCO', 'WSIB', 'CalSTRS').

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / lp_name / description
      Previous value: -"LP name or common acronym (e.g. 'CalPERS', 'WSIB', 'Ford Foundation', 'Bessemer Trust', 'HarbourVest')."New value: +"Investor name or common acronym (e.g. 'Surdna Foundation', 'UTIMCO', 'WSIB', 'CalSTRS')."
  2. First observed

TDQS

A3.5/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 the full behavioral burden. 'Retrieve' plus the enumeration of returned data conveys that this is a broad composite read, but nothing is said about permissions, whether a missing LP errors versus returns empty, latency/cost of assembling a full dossier, or freshness of filing-derived figures. The enumerated output scope adds real value beyond a bare name, but the operational profile is undocumented.

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?

Front-loaded with verb and resource before the field enumeration, and every listed item (AUM, pacing, consultants, IRR/TVPI/DPI, holdings) is a genuine selection signal rather than filler. The single sentence is long and comma-chained, which makes it dense to scan, but no clause is wasted.

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 no output schema, the description does the necessary work of specifying what comes back, and it does so in detail. For a single-parameter tool with full schema coverage, the only material omission is behavioral — error handling and cost/permission expectations — since annotations are absent.

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?

There is one parameter and schema description coverage is 100% — the schema already explains lp_name and even supplies acronym examples ('UTIMCO', 'WSIB', 'CalSTRS'). The description adds only 'for a specific Limited Partner', which restates rather than extends the schema. High coverage puts the baseline at 3.

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?

States a specific verb ('Retrieve') and a specific resource ('complete Prilago Investor Profile for a specific Limited Partner'), then enumerates the exact contents (AUM, pacing plan, consultants, Net IRR/TVPI/DPI, fund holdings, filing signals). This is far more than a restatement of the name and lets an agent distinguish it from the lookups implied by siblings like search_lps or get_breaking_lp_signals. It stops short of explicitly naming an alternative, so a 4 rather than a 5.

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 only implied: the phrase 'for a specific Limited Partner' signals a one-LP, name-keyed deep profile, which contrasts implicitly with narrower sibling lookups. There is no explicit when-to-use, when-not-to-use, or named alternative anywhere in the text. An agent must infer the routing decision from the field enumeration alone.

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