Skip to main content
Glama
Lucacelli B2B MCP Server

Lucacelli B2B MCP Server

PitchBook & Crunchbase Alternative — SEC Form D Funded Startups

scrape_funded_startups_sec_form_d
Read-onlyIdempotent

Find newly funded US startups from real-time SEC Form D filings and enrich them with raised amounts, founder contacts, domains, and verified emails by industry keywords.

Instructions

Find newly funded startups via real-time US SEC Form D filings + web enrichment: extract exact USD raised, founder/executive names, direct phone numbers, domains, and verified emails ($0.80/1k).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "keywords": "<keywords>"
    },
    "name": "scrape_funded_startups_sec_form_d"
  }
}

Input Schema

NameRequiredDescriptionDefault
keywordsYesIndustry keywords in Form D filings, e.g. ["Software", "Artificial Intelligence"]
startDateNoMinimum filing date (YYYY-MM-DD)2025-06-01
maxCompaniesNoMaximum funded startups

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world), so the description's job is to add what they cannot. It does so by disclosing enrichment outputs — phone numbers, verified emails, domains — plus an explicit price point ($0.80/1k), which is a real behavioral consideration for a paid scraper. It omits enrichment failure rates and how 'verified' emails are determined.

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?

A single front-loaded sentence that leads with the action and data source before the enrichment and pricing claims. Slightly dense with output claims folded into the purpose statement, but no sentence is wasted.

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?

With no output schema, the description usefully names the returned fields (USD raised, founder names, phones, domains, emails), which the agent would otherwise have to discover empirically. Combined with annotation-covered safety and a fully documented 3-param schema, it is largely complete; only cost-scaling and result-volume behavior are left implicit.

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%, with all three parameters documented including a date example and defaults, so the schema carries the semantic load. The description adds no parameter-level guidance — it describes outputs rather than inputs and does not advise on keyword granularity or the tradeoff of raising maxCompanies.

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 ('Find newly funded startups') plus the distinguishing data source (real-time US SEC Form D filings), which separates it from job-board or YC-style siblings such as scrape_wellfound_yc_startup_jobs. An agent can identify this as the funding-event discovery tool without opening the schema.

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?

The 'PitchBook & Crunchbase Alternative' framing implies when to reach for it (replacing paid startup databases), but there is no explicit when-not guidance, no named sibling alternative, and no prerequisites such as keyword breadth or date-window expectations. Usage is inferable but not stated.

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