Skip to main content
Glama

Prilago Institutional LP & GP Fundraising Intelligence

get_breaking_lp_signals

Query Prilago's LP Filing & News Feed across SEC Form D XML filings, primary LP board/ACFR PDFs, and labeled trade-press items for disclosed fund commitments, pacing plans, RFPs, and CIO transitions.

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

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of recent signals to return (1 to 30, default 12).
queryNoOptional keyword, strategy, LP name, or GP name filter.
signal_typeNoOptional signal type filter (e.g. 'Commitment', 'RFP', 'Pacing', 'Leadership').

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / query / description
      Previous value: -"Optional keyword, strategy, LP name, or GP name filter (e.g. 'Healthcare', 'RFP', 'Private Credit')."New value: +"Optional keyword, strategy, LP name, or GP name filter."
    • changedInput schema / properties / signal_type / description
      Previous value: -"Optional signal type filter (e.g. 'New Commitment', 'RFP', 'Pacing', 'Leadership')."New value: +"Optional signal type filter (e.g. 'Commitment', 'RFP', 'Pacing', 'Leadership')."
  2. First observed

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It identifies the data sources and signal types but does not state whether the operation is read-only, how fresh the signals are, whether results are paginated, or what the response contains.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single dense sentence that front-loads the core action and resource, then lists sources and signal types without redundant wording. Every clause contributes to scope.

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 three-parameter query tool with no annotations and no output schema, the description covers the data domain well but omits return format, freshness, and pagination behavior. It is adequate to understand the tool's scope but not fully complete for reliable invocation.

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 input schema already documents limit, query, and signal_type. The description mentions signal categories that map to signal_type but adds no syntax, format, or filtering semantics beyond what the schema provides.

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 states a specific verb (Query) and resource (Prilago's LP Filing & News Feed), and enumerates the source types and signal categories it covers. It is clear what the tool does, though it does not explicitly differentiate itself from sibling tools such as search_lps or get_lp_360_dossier.

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?

The description explains what data is queried but gives no guidance on when to use this tool versus alternatives, nor any exclusions or prerequisites. An agent must infer usage context from the name and sibling list 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