Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

datasets_pitchbook_funds_search

Search public PitchBook fund profiles by keyword, status, strategy, or vintage year, and sort results to find relevant funds for research or deal sourcing.

Instructions

Search PitchBook funds dataset. Searches the crawled public PitchBook fund profile catalog stored in a search index. Discovered from PitchBook's public sitemap. Sort enum: relevance, name_asc, vintage_desc, recently_crawled_desc.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoFull-text query over name and description, max 256 characters
pageNoPage number, defaults to 1
sortNoSort enum: relevance, name_asc, vintage_desc, recently_crawled_desc
run_idNoExact crawl run-id filter, max 128 characters
page_sizeNoPage size, defaults to 20 and maxes at 100; page * page_size must be <= 10000
fund_statusNoExact fund status filter (e.g. Closed, Raising), max 128 characters
fund_strategyNoExact fund strategy filter (e.g. Early Stage VC, Buyout), max 128 characters
max_vintage_yearNoMaximum vintage year
min_vintage_yearNoMinimum vintage year

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / sort / enum
      Added value: +[
+  "relevance",
+  "name_asc",
+  "vintage_desc",
+  "recently_crawled_desc"
+]
  2. Added

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It states the source of data and mentions sort options, but does not disclose important behaviors like pagination limits, result structure, rate limits, or that it is read-only. The page and page_size parameters are already in the schema, so the description adds little beyond that.

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 description is concise and front-loaded with the main action. It is three sentences long, but the third sentence listing the sort enum is redundant with the schema and adds little value. Still, it is not bloated and the core purpose is clearly stated upfront.

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

Completeness2/5

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

For a search tool with 9 optional parameters and no output schema, the description is incomplete. It does not explain what results look like, how pagination works beyond parameter names, or when to use this instead of the facets or item tools. Given the complexity and sibling tools, an agent would need more context to use it effectively.

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 all 9 parameters are documented in the schema. The description does not add any additional meaning beyond restating the sort enum, which is already in the schema. It neither clarifies usage nor provides examples, so it meets the baseline for high coverage.

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 clearly states the tool searches the PitchBook funds dataset, specifying it is a full-text search over a crawled catalog. It is distinct from other tools in that it is a search operation, but it does not explicitly contrast with sibling search tools like datasets_pitchbook_funds_facets or datasets_pitchbook_funds_item, so it lacks explicit sibling differentiation.

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 provides no guidance on when to use this tool versus alternatives such as the facets or item tools. It does not state any conditions, exclusions, or mention other tools that might be more appropriate for specific queries. An agent would not know when to choose this over the many sibling search tools.

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

Deploy Server

Other Tools