Skip to main content
Glama
@corridordata/mcp-server

@corridordata/mcp-server

Official
by corridordata

search_funded_startups

Read-onlyIdempotent

Find newly funded US and cross-border startups from SEC EDGAR Form D filings, including amounts raised, domains, executive names, and exclusion of pooled funds/real estate.

Instructions

Extract newly funded US and cross-border startups from official SEC EDGAR Form D XML filings with USD raised, pooled hedge-fund/real-estate filtering, resolved company domains, and CEO/Founder/Director names (corridordata/sec-form-d-startup-funding-leads).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_funded_startups"
  }
}

Input Schema

NameRequiredDescriptionDefault
statesNoOptional 2-letter US state codes (e.g. ['CA', 'NY', 'TX', 'MA']).
maxItemsNoMaximum number of funded startup Form D records to return.
filedWithinDaysNoLookback window in days for SEC EDGAR Form D filings.
maxTotalChargeUsdNoOptional per-run USD spend cap forwarded to Apify Pay-Per-Event billing (`maxTotalChargeUsd`).
minAmountRaisedUsdNoMinimum USD sold/offering amount (e.g. 500000 for Seed/Series A+).
enrichCompanyDomainNoAutomatically resolve root company website domains.
techAndHealthcareOnlyNoRestrict to Technology, SaaS, AI, Biotech, Pharmaceuticals, and Healthcare issuers.
excludePooledFundsAndRealEstateNoExclude hedge funds, PE vehicles, and real estate syndications.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world behavior, so the safety profile is covered. The description adds genuinely new context: the data source is official SEC EDGAR Form D XML (self-reported filings), amounts are in USD, hedge-fund/PE/real-estate vehicles are filtered out, and domains and executive names are resolved. It does not discuss result freshness, pagination, or cost behavior beyond what the schema's maxTotalChargeUsd already states.

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?

It is a single front-loaded sentence that leads with the action and resource before listing capabilities, so the most important information comes first. It is dense and feature-list-like, and the embedded dataset slug ('corridordata/sec-form-d-startup-funding-leads') is of marginal use to an agent selecting the tool, but there is little outright waste.

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

Completeness5/5

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

With eight optional parameters, 100% schema coverage, and rich annotations, the remaining burden on the description is to explain source, scope, and what the returned records contain. It does all three (Form D filings, US plus cross-border, amounts, domains, executive roles), and no output schema exists, so nothing critical is missing for correct invocation.

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 coverage is 100%, so all eight parameters are already documented with defaults and bounds, making 3 the baseline. The description reinforces the meaning of a few of them (minAmountRaisedUsd via 'USD raised', excludePooledFundsAndRealEstate via 'pooled hedge-fund/real-estate filtering', enrichCompanyDomain via 'resolved company domains') but adds no format, precedence, or interaction details beyond the schema text.

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?

The description gives a specific verb ('Extract') and a precise resource ('newly funded US and cross-border startups from official SEC EDGAR Form D XML filings'), plus the distinguishing enrichment scope (USD raised, domain resolution, executive names). It is clearly distinct from the sibling tools, which cover jobs, grants, tenders, and trials, so an agent can route to it without inspecting 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?

Usage is only implied: the description and defaults (filedWithinDays=7, excludePooledFundsAndRealEstate=true) suggest a 'find recently funded startup leads' scenario, but there is no explicit when-to-use, when-not-to-use, or named alternative. Nothing tells the agent whether to prefer this over a general SEC filing search or a grants/tenders tool for pipeline sourcing.

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