Skip to main content
Glama

GP Intel

by io.github.gparientee

Search PE investments across all firms

search_deals
Read-only

Cross-firm investment search across ALL European PE firms: filter portfolio companies by entry year (or range), sector, geography and status (active/exited). Set group_by to count instead of list, e.g. answers 'how many French healthcare companies were PE-backed in 2024 across all firms'. Buyer names and MOIC stay locked unless authenticated as Pro.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
gpNoOptional: restrict to one PE firm by name
geoNoCompany geography filter, e.g. 'France' (exact, case-insensitive)
yearNoExact entry year, e.g. 2024
limitNoPage size for list mode (max 50)
offsetNoPagination offset for list mode
sectorNoSector filter, e.g. 'Healthcare' (exact, case-insensitive)
statusNoFilter: only active holdings or only exited positions
year_toNoEntry year range end (ignored if year is set)
group_byNoReturn counts grouped by this dimension instead of a list of deals
year_fromNoEntry year range start (ignored if year is set)

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, indicating safe read. Description adds that buyer names and MOIC are locked unless Pro authenticated, which is useful behavioral context beyond annotations. No contradictions found.

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?

Two sentences, front-loaded with main purpose. No redundant words; every sentence adds value. Highly efficient.

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?

Covers main use cases, filtering options, and authentication caveat. Lacks explanation of return format (list of deals vs counts), but as there is no output schema, this is acceptable. For a complex 10-parameter tool, description is fairly comprehensive.

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 parameters are already documented. Description adds context for group_by usage and authentication locking, which extends schema meaning. Baseline 3 is appropriate; description does not significantly enhance param semantics.

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?

Description starts with 'Cross-firm investment search across ALL European PE firms', clearly stating the broad scope and distinguishing from sibling per-firm tools like gp_portfolio. It lists specific filters (entry year, sector, geography, status) and modes (list vs group_by).

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

Usage Guidelines4/5

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

Provides explicit usage example with group_by ('how many French healthcare companies...') and mentions authentication requirements for buyer names and MOIC. However, it does not explicitly state when to avoid this tool or compare to siblings like search_exits or who_owns.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All GP Intel toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation5/5

Each tool has a unique purpose: gp_exits and gp_portfolio are per-firm, while search_exits and search_deals are cross-firm, clearly differentiated by scope. search_companies, search_gps, and who_owns cover distinct entity types and actions, leaving no ambiguity.

Naming Consistency3/5

Tool names use a consistent verb_noun pattern for search_* tools and a gp_* prefix for per-firm tools, but who_owns breaks the convention with a question phrase. The inconsistency is noticeable but does not severely impair usability.

Tool Count5/5

With 7 tools, the server is well-scoped for its domain, covering per-firm and cross-firm queries, entity searches, and ownership history without redundancy or bloat.

Completeness4/5

The toolset covers the core private equity data needs: searching firms and companies, viewing portfolios and exits for a specific GP, cross-firm deal and exit searches, and ownership lookup. Minor gaps like detailed company financials are outside the apparent scope.

Resources