Skip to main content
Glama

Prilago Institutional LP & GP Fundraising Intelligence

get_consultant_gatekeeper_clients

Query Prilago's Investment Consultant & OCIO Graph to map which institutional LPs each consultant advises and their disclosed room under target allocation.

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

Input Schema

NameRequiredDescriptionDefault
consultant_nameNoConsultant firm name (e.g. 'Aksia', 'Meketa', 'Cambridge Associates'). Leave empty to list top consultants.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / consultant_name / description
      Previous value: -"Consultant firm name (e.g. 'Aksia', 'Meketa', 'Cambridge Associates'). Leave empty to rank all top gatekeepers."New value: +"Consultant firm name (e.g. 'Aksia', 'Meketa', 'Cambridge Associates'). Leave empty to list top consultants."
  2. First observed

TDQS

B3.2/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 burden; it implies a read-only graph query but never states that explicitly. It does add one useful behavioral nuance by saying 'disclosed' room, flagging that coverage is limited to voluntarily disclosed data. It says nothing about result size, ranking, or whether results are capped/paginated for the empty-parameter 'top consultants' mode.

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?

One front-loaded sentence with the resource and the payoff stated up front and no filler. It is dense with domain jargon ('disclosed room under target allocation') that could cost an agent a beat of interpretation, but nothing is redundant.

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-optional-parameter read tool with no output schema, the description adequately conveys what comes back (LP-to-consultant mapping plus allocation room). The main residual gap is that without annotations or an output schema, the agent gets no sense of result shape or size, and the empty-parameter behavior is only documented in the schema.

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 coverage is 100% and the single parameter is already fully documented with examples ('Aksia', 'Meketa', 'Cambridge Associates') and the empty-value behavior. The description adds only indirect meaning, clarifying that the consultant is the entry point for mapping advised LPs. Baseline 3 is appropriate since the schema does the heavy lifting.

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 ('Query') and a specific resource (Prilago's Investment Consultant & OCIO Graph) and then states the concrete output: which institutional LPs each consultant advises plus their disclosed room under target allocation. That is clearly differentiated from LP-centric siblings like search_lps or match_fund_to_lps by its consultant-first orientation, though it never names an alternative explicitly.

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 when-to-use or when-not-to-use guidance and no mention of alternatives among the sibling tools (get_lp_360_dossier, match_fund_to_lps, get_breaking_lp_signals). A user must infer from the phrase 'room under target allocation' that this suits consultant-channel prospecting rather than direct LP search. Only the schema's 'Leave empty to list top consultants' hints at a usage mode.

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