Skip to main content
Glama

Search LP records

search_lps
Read-onlyIdempotent

THEN: return limited partner records (name, slug, LP type, HQ country and city, geographic focus, website, emerging-manager backing, verified flag, and michael_network: {has_warm_path: boolean, matches?}) filtered by country, LP type and emerging-manager backing, at most 25 per call. has_warm_path is free and unconditional on every caller; when true, a Pro/Enterprise caller also gets the matched contact's name in matches, everyone else gets a teaser (no content, just confirmation it exists) pointing at request_warm_intro or the LP's own page -- credits, not a subscription, unlock it. This is Michael Schneider's own personal network, not a data-matching feature; no data source is ever named. Set backs_emerging_managers=true to see only LPs that have already backed a first or second fund — for a first-time manager that is usually the only filter that matters. Billed exactly like get_fund, per caller: no key, 10 free calls per UTC day (the same pool as every keyless tool); a free/Starter/Pro key draws from a shared monthly "profile pull" allowance with get_fund, and search_lps counts one pull per LP row returned (Free 20/mo, Starter 200/mo, Pro unlimited with a fair-use limit of 500 LP rows per UTC day per key, error_reason fair_use_daily_lp_rows). If the allowance runs short the page is cut to what remains (truncated_reason "pull_quota") instead of failing; at zero you get pull_quota_exceeded with pulls_used, pulls_limit and upgrade_url. LP Radar is included in Pro, there is no separate subscription. An agent key is billed per LP returned at the same per-row price as search_funds (EUR 0.01 per row), with no monthly cap since every row is paid. Use check_lp_coverage first — it is free and unmetered, and tells you whether the dataset covers your geography and LP type before you call this. website is null when no website is on record; it is never omitted. Cost: free with no key (10 keyless calls per day, one shared pool); a free/Starter/Pro key draws from the same monthly "profile pull" allowance as get_fund, one pull per LP row (Free 20/mo, Starter 200/mo, Pro unlimited with a fair-use limit of 500 LP rows per UTC day); LP Radar is included in Pro. An agent key is billed per LP returned at the same per-row price as search_funds (1 credit, EUR 0.01 each), with no monthly cap since every row is paid.

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
limitNoRecords to return, 1-25. A value above 25 is rejected, not clamped.
countryNoHeadquarters country of the LP, spelled out in full (e.g. 'Germany'). Two-letter ISO codes are accepted too.
lp_typeNoLP type. Must be one of the listed values; common spellings such as 'family office' or 'pension' are accepted and normalised.
backs_emerging_managersNotrue returns only LPs that have backed an emerging manager; false returns only those that have not. Omit for both. Not available on check_lp_coverage, which reports the figure as a breakdown instead.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / backs_emerging_managers
      Added value: +{
      +  "description": "true returns only LPs that have backed an emerging manager; false returns only those that have not. Omit for both. Not available on check_lp_coverage, which reports the figure as a breakdown instead.",
      +  "type": "boolean"
      +}
  2. Added

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the read-only annotations, it discloses conditional warm-path entitlements, teaser behavior, per-row and shared-pool metering, fair-use limits, and the nullable website field. Particularly useful are the partial-success behavior when quota remains, the pull_quota truncation reason, and the pull_quota_exceeded response at zero allowance.

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

Conciseness2/5

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

The core operation is front-loaded, but the definition is excessively long and difficult to scan. The final Cost section substantially repeats the immediately preceding billing details, and the orphaned opening 'THEN:' adds awkwardness without value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite having no output schema, the description supplies the result fields, conditional matches behavior, null handling, result limits, quota truncation, error reasons, and relevant plan-dependent costs. Together with the schema and safety annotations, this gives an agent more than enough context to select and invoke the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 100%, and much of the opening filter summary repeats that structured information. The description nevertheless adds meaningful semantics for backs_emerging_managers by explaining backing of a first or second fund and recommending the filter for first-time managers.

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?

The description clearly states that the tool returns limited partner records, enumerates the principal result fields, and identifies the country, LP type, and emerging-manager filters plus the 25-record cap. It also functionally distinguishes the precheck role of check_lp_coverage from this record-retrieval tool.

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

Usage Guidelines5/5

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

It explicitly instructs agents to use the free, unmetered check_lp_coverage first to validate geography and LP-type coverage. It also gives concrete filter guidance for first-time managers and explains when matches lead toward request_warm_intro rather than providing contact content directly.

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.