Skip to main content
Glama
mcp-public-intel

mcp-public-intel

by pecopeko

sec_form_d_funding_search

Search recent SEC EDGAR Form D and D/A filings to find private startup and venture capital funding by keyword, company, or date range without an API key.

Instructions

Search official SEC EDGAR Full-Text Search (efts.sec.gov) for recent Form D and Form D/A private startup funding & venture capital filings. Zero API key required.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of Form D filings to return (1-50, default 15).
queryNoOptional search keyword, sector, or company name (e.g. 'artificial intelligence', 'robotics').
date_toNoOptional end filing date in YYYY-MM-DD format.
date_fromNoOptional start filing date in YYYY-MM-DD format.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/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 behavioral burden. It usefully discloses the official source, no-API-key requirement, and filing types, but it does not describe result ordering, pagination, rate limits, or return shape.

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?

The description is two tight sentences with the core purpose and authentication detail front-loaded. There is no filler or repetition.

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 simple read-only search tool with fully documented parameters, the description gives enough context to call it correctly: source, filing types, recency, and no key requirement. It could be stronger by mentioning what each result contains, especially since there is no output schema.

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 the parameters are already well documented in the schema. The description adds little parameter-specific meaning beyond the general goal of finding recent funding filings.

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 states a specific verb and resource: search SEC EDGAR Full-Text Search for Form D and Form D/A filings. It also scopes the purpose to private startup funding and venture capital filings, making the tool's role unambiguous.

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?

It clearly says to use this for recent Form D and Form D/A funding filings, which gives an agent a concrete use case. It does not name exclusions or alternatives, but the sibling tools listed are unrelated domains, so the lack of explicit alternatives is less problematic.

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