Skip to main content
Glama

Check LP coverage

check_lp_coverage
Read-onlyIdempotent

START HERE for any question about limited partners (LPs). Answers "does Fund Momentum cover my geography and LP type" with COUNTS ONLY: how many disclosed LPs match, how many of those have backed emerging managers, and how many have a known warm path in Michael's own network (known_warm_path). It never returns a name, slug, website or commitment. COST: free, works with no API key at all (counts against the keyless daily allowance), and is never billed to agent credits or a monthly quota. Counts below 5 are reported as "<5" and zero as "none". Call this before search_lps to find out whether LP Radar covers what you need. Cost: free. Never billed to agent credits or a monthly quota; counts against the keyless allowance of 10 calls per day.

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

Input Schema

NameRequiredDescriptionDefault
countryNoHeadquarters country of the LP, spelled out in full (e.g. 'Germany', 'United States'). Two-letter ISO codes are accepted too. LPs whose headquarters is undisclosed are never counted under a country; they are reported separately as undisclosed_hq_count.
lp_typeNoLP type. Must be one of the listed values; common spellings such as 'family office', 'pension' or 'fund of funds' are accepted and normalised.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the readOnly/idempotent/closed-world annotations: it discloses the output contract (counts only, no names or commitments), small-count suppression ('<5' and 'none'), the keyless 10-calls-per-day allowance, and that calls are never billed to agent credits or quota. This is exactly the cost and disclosure context annotations cannot express.

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?

The entry-point cue, output contract, and cost are front-loaded and easy to scan. The cost statement is, however, repeated at the end ('Cost: free. Never billed to agent credits or a monthly quota...') after already appearing inline, which is a small redundancy.

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?

For a two-optional-parameter, read-only counting tool with no output schema, the description supplies everything an agent needs: what is counted, what is withheld, how edge cases are bucketed, cost/quota behaviour, and the sibling call order. Nothing material is missing.

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 country and lp_type descriptions already explain full-name spelling, ISO acceptance, undisclosed_hq_count, and enum normalisation. The tool description only alludes to the filters at a high level ('my geography and LP type'), so it adds little beyond the schema; baseline 3 applies.

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?

States a specific verb and resource ('Answers "does Fund Momentum cover my geography and LP type" with COUNTS ONLY') and immediately scopes what it will not return (name, slug, website, commitment). An agent can distinguish this from search_lps without opening either schema, and 'START HERE for any question about limited partners' front-loads the entry point.

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?

Explicit routing instruction: 'Call this before search_lps to find out whether LP Radar covers what you need' names the alternative sibling and the condition that selects it. Both parameters are optional, and the description makes clear the tool is a cheap pre-flight check rather than the search itself.

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.