Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

datasets_pitchbook_advisors_search

Search PitchBook advisors dataset. Searches the crawled public PitchBook advisor (service provider — e.g. investment bank, lender, financing advisory firm) profile catalog stored in a search index.

Instructions

Search PitchBook advisors dataset. Searches the crawled public PitchBook advisor (service provider — e.g. investment bank, lender, financing advisory firm) profile catalog stored in a search index. Discovered from PitchBook's public sitemap. Sort enum: relevance, name_asc, year_founded_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, year_founded_desc, recently_crawled_desc
run_idNoExact crawl run-id filter, max 128 characters
hq_stateNoExact headquarters state/region filter, max 128 characters
page_sizeNoPage size, defaults to 20 and maxes at 100; page * page_size must be <= 10000
hq_countryNoExact headquarters country filter, max 128 characters
service_typeNoExact service provider type filter (e.g. Commercial Bank, Investment Bank, Financing Advisory), max 128 characters
max_year_foundedNoMaximum founding year
min_year_foundedNoMinimum founding 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",
+  "year_founded_desc",
+  "recently_crawled_desc"
+]
  2. Added

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden, and it does disclose a genuinely important behavioral trait: 1 credit per record returned with a 2-credit minimum (empty result costs 2, full page of 100 costs 100). That is real cost context an agent needs before calling. It still omits auth requirements, return field shape, and pagination edge behavior.

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?

Purpose is front-loaded, then provenance, then the sort enum, then billing in descending priority. Sentences are tight, though the sort enum listing duplicates the schema's enum and is wasted text.

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?

For a 10-parameter search tool with no output schema and no annotations, the description covers the entity, the data origin, sortable dimension, and cost model. Return value shape is not described, but it is reasonable to expect the paired _item tool for detail retrieval, leaving this adequately complete.

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 ten parameters are already documented in the schema, establishing a baseline of 3. The description only restates the sort enum, which the schema already provides, adding no syntax, format, or filtering nuance beyond it.

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 advisors dataset') and defines what the advisors entity is (service providers like investment banks, lenders, financing advisory firms). The entity framing implicitly separates it from sibling pitchbook searches (companies, funds, investors), though it never explicitly contrasts them.

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

Usage Guidelines3/5

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

Usage is implied by 'Search' and the entity description, but there is no explicit when-to-use or when-not-to-use guidance and no routing to the neighboring datasets_pitchbook_advisors_item or datasets_pitchbook_advisors_facets tools. The billing note hints that deliberation is warranted but is not framed as usage advice.

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