Skip to main content
Glama

Find companies raising private capital (SEC Form D)

find_funding_leads
Read-onlyIdempotent

Recent SEC Form D filings: companies that just raised or are raising private capital, with offering size, amount sold, investors count, industry, state and the SEC filing link. Use for startup funding leads and deal sourcing. Official EDGAR data, issuer-level only. Max 10 rows per call; window up to 14 days.

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": "find_funding_leads"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoFiled in the last N days (default 5).
limitNoRows to return (default 10).
stateNoTwo-letter issuer state codes.
date_toNoWindow end, YYYY-MM-DD (default today).
industryNoIndustry group contains, e.g. "technology".
date_fromNoWindow start, YYYY-MM-DD.
young_onlyNoOnly companies incorporated within five years.
include_fundsNoInclude pooled investment funds (excluded by default).
name_containsNoIssuer name contains.
max_offering_usdNoMaximum total offering amount in USD.
min_offering_usdNoMinimum total offering amount in USD.
include_amendmentsNoInclude Form D/A amendments.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint and idempotentHint, so the description is not carrying the safety burden. It still adds real behavioral context beyond those: hard caps of 10 rows per call and a 14-day maximum window, EDGAR as the provenance, and a stated scope limit (issuer-level only). It does not mention pagination or what happens when the cap truncates a larger result set, keeping it out of the top band.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences: first the data and returned fields, then the use case, then the data source, scope and hard limits. Nothing is redundant and the most important identification detail is front-loaded before the operational constraints.

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 12 parameters, no output schema and no required fields, the description compensates well by listing the returned fields and disclosing the row/window caps. What it leaves unaddressed is the default filter behavior when no parameters are supplied beyond what the schema notes, plus any result truncation semantics — minor gaps for a read-only discovery tool.

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 12 parameters are already documented, and the description adds no per-parameter syntax or format guidance. The only overlapping hints — the 10-row cap and 14-day window — merely restate constraints already present in the schema's maximum values. Baseline 3 is appropriate when the schema does the heavy lifting.

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 opening sentence names a specific source and resource — recent SEC Form D filings for companies that just raised or are raising private capital — and enumerates the returned fields (offering size, amount sold, investor count, industry, state, filing link). This is clearly distinguishable from siblings like find_insider_trades or find_new_business_registrations without opening any schema.

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

Usage Guidelines4/5

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

"Use for startup funding leads and deal sourcing" gives a concrete selection context, and "issuer-level only" plus "Official EDGAR data" scopes what kind of entity the results represent. However, no alternative tool is named and no explicit when-not condition is stated, so the agent must infer the boundary against sibling tools itself.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources