Skip to main content
Glama

Kaleidoscope MCP (SEC & financial data)

Form D Flow (SEC private-offering pulse by month, PIT-clean, w/ breakdown) [beta]

mars_form_d_flow
Read-onlyIdempotent

Aggregate SEC Form D private-offering flow as a time series — "how much private capital was raised via Reg D exemptions by month?" — with industry / jurisdiction / entity-type breakdowns. The cleanest PIT-anchored private-capital pulse mars ships: every row is a real SEC filing, so filing_date is a genuine point-in-time date (the day it hit EDGAR), with no extraction ambiguity, no dedup, and no coverage cliff. 765K filings (410K of them pooled-fund), 2006 → today.

Required: from_date + to_date (max 20-year window) + bucket (week|month|quarter|year). Optional: industry (industry_group_type exact — the live values are descriptive title-case strings, e.g. 'Other Technology', 'Commercial', 'Biotechnology', 'Oil and Gas', 'REITS and Finance', 'Residential', 'Other Health Care', 'Investing', 'Manufacturing', 'Other' — NOT uppercase codes), jurisdiction_of_inc (FULL UPPERCASE name, e.g. 'DELAWARE' / 'TEXAS' / 'CALIFORNIA' / 'NEVADA' / 'BRITISH COLUMBIA, CANADA' — NOT a 2-letter code), entity_type ('Corporation' / 'Limited Liability Company' / 'Limited Partnership' / 'Business Trust' — LP is a decent fund-vehicle proxy), breakdown_by (industry|jurisdiction|entity_type|fund_type), as_of (PIT gate on filing_date).

Contracts: (1) NO integrity_tier filter — Form D rows are SEC-clean by construction. (2) exclude_amendments defaults true — amendments are retroactive updates that would double-count. (3) total_offering_amount = the offering REGISTERED (a ceiling, not necessarily raised); total_amount_sold = raised as of the filing date (can grow via later amendments). Report both; don't call the offering amount 'raised.' (4) as_of gates filing_date <= as_of — a past as_of reconstructs the pulse as it was knowable then, leak-free.

Fund flows (2026-07-18): fund_type ('Hedge Fund' / 'Private Equity Fund' / 'Venture Capital Fund' / 'Other Investment Fund' — exact title-case) + is_pooled_fund (bool) are now populated (410K pooled filings, ~54% of corpus), so PE/VC/Hedge private-fund flow is one query — e.g. fund_type='Venture Capital Fund' for the VC-fund-formation pulse; each bucket also carries n_pooled_funds. Complements mars_sector_funding_flow (news-extracted operating raises); the two are NOT summable.

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": {
      "from_date": "<from_date>",
      "to_date": "<to_date>",
      "bucket": "<bucket>"
    },
    "name": "mars_form_d_flow"
  }
}

Input Schema

NameRequiredDescriptionDefault
as_ofNoISO 8601 UTC PIT gate on filing_date. Default now().
bucketYesBucket size. Required.
to_dateYesYYYY-MM-DD. Required. Must be > from_date; max 20-year window.
industryNoindustry_group_type exact match — descriptive title-case (e.g. 'Other Technology', 'Commercial', 'Biotechnology', 'Oil and Gas').
from_dateYesYYYY-MM-DD. Required. Lower bound on filing_date.
fund_typeNoPooled-vehicle fund type, EXACT title-case: 'Hedge Fund' / 'Private Equity Fund' / 'Venture Capital Fund' / 'Other Investment Fund'. Only pooled filings carry it (~54% of corpus).
entity_typeNoFiler entity type ('Corporation' / 'Limited Liability Company' / 'Limited Partnership' / 'Business Trust').
breakdown_byNoSplit each bucket by this dimension (one flat row per bucket × value).
is_pooled_fundNotrue = pooled investment vehicles only; false = operating-company/other. Omit for both.
exclude_amendmentsNoExclude amendment filings (retroactive updates). Default true — set false to include.
jurisdiction_of_incNoFull UPPERCASE jurisdiction of incorporation, e.g. 'DELAWARE' / 'TEXAS' / 'CALIFORNIA' / 'NEVADA' / 'BRITISH COLUMBIA, CANADA'. Not a 2-letter code.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Goes well past the readOnly/idempotent annotations by disclosing coverage (765K filings, 410K pooled, 2006→today), why no integrity_tier filter is needed, the double-count risk from amendments, the semantic ceiling-vs-actual distinction on the two amount fields, and the leak-free reconstruction semantics of as_of. These are exactly the behavioral traits an agent cannot infer from structured fields.

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?

Structure is strong — headline purpose first, then Required/Optional, then Contracts, then fund-flow notes — and nearly every line carries operational information. It is nonetheless long, and the repeated inline lists of industry/jurisdiction/entity_type/fund_type values restate the schema, adding bulk an agent does not strictly need.

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?

Covers the hard parts of an 11-parameter, no-output-schema tool: window limits, bucket requirement, amendment handling, PIT gating, and how breakdown_by reshapes output into one row per bucket × value. It stops short of the full return shape (currency/units, whether n_pooled_funds appears without breakdown_by, row-count or pagination behavior), which matters more here because no output schema exists.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 100% schema description coverage the baseline is 3, and the description adds genuine meaning beyond the schema: that industry values are title-case descriptive strings not uppercase codes, that jurisdiction is a full uppercase name not a 2-letter code, that 'Limited Partnership' is a usable fund-vehicle proxy, and that as_of is a PIT gate on filing_date. Much of the enum enumeration duplicates the schema verbatim, which keeps it out of the top score.

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?

Opens with a specific verb+resource ('Aggregate SEC Form D private-offering flow as a time series') and immediately frames the question it answers ('how much private capital was raised via Reg D exemptions by month?'). It also distinguishes itself from the closest sibling by naming mars_sector_funding_flow and stating the two are NOT summable.

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

Usage Guidelines5/5

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

Routes the agent explicitly: use this for Reg D/Form D private-offering volume, use mars_sector_funding_flow for news-extracted operating raises, and never combine them. It also gives conditional guidance inside the contracts — default exclude_amendments=true to avoid double-counting, and report total_offering_amount vs total_amount_sold rather than conflating them.

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