Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

datasets_pitchbook_funds_search

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.

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. Billing: this search costs 1 credit per record returned, with a minimum of 2 (an empty result costs 2, a full page of 100 costs 100).

Input 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

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose a genuinely useful behavioral trait: the per-record credit cost with a minimum of 2 credits (empty result = 2, full 100-record page = 100). It does not cover auth requirements, return shape, or pagination behavior beyond what the schema shows.

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?

Front-loaded with the core purpose, then provenance, then sort, then billing in a logical order. Slightly padded by repeating the sort enum already present in the schema, but otherwise tight and waste-free.

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 nine-parameter search tool with no annotations and no output schema, the description covers purpose, data provenance, and the cost model. It stops short of sibling routing and return-format expectations, leaving some gaps an agent would want filled.

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 nine parameters are already documented, and the description's restatement of the sort enum is redundant. The billing note implicitly informs page_size trade-offs but adds no syntax or meaning beyond the schema. Baseline 3 applies.

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?

States a specific verb and resource ('Search PitchBook funds dataset') and adds provenance ('crawled public PitchBook fund profile catalog ... Discovered from PitchBook's public sitemap'), which clarifies scope. It does not, however, distinguish itself from siblings like datasets_pitchbook_funds_item (detail) or datasets_pitchbook_funds_facets.

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?

No explicit when-to-use guidance and no named alternatives. An agent isn't told to reach for this search versus the item/facets siblings, or when a query-less call is appropriate. Only billing conditions are given, which is cost context rather than usage routing.

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