Skip to main content
Glama

Sec Form D

by io.github.pipeworx-io

Form D Recent Raises

form_d_recent_raises
Read-onlyIdempotent

Recent SEC Form D exempt-offering notices, newest first, hydrated from official filing XML with offering amount, amount sold, investors, security types, industry, issuer and related persons. A Form D is a self-reported offering notice—not proof that a financing round closed. Amendments are labeled and must not be double-counted.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysNoLook back this many days from `until` instead of supplying `since` (1-3650). An explicit `since` wins.
limitNoResults to hydrate and return (1-10, default 8).
sinceNoStart filing date YYYY-MM-DD. Default 7 days ago.
untilNoEnd filing date YYYY-MM-DD. Default today.
industryNoOptional case-insensitive industry substring, e.g. "Biotechnology".
min_amountNoAlias for `minimum_sold`: minimum reported amount sold in USD.
minimum_soldNoOnly return offerings reporting at least this much sold, in USD. Also accepted as `min_amount`.
include_amendmentsNoInclude amended notices (default true).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
returnedYes
offeringsYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed4 schema fields changed
    • changedInput schema / examples
      Previous value: -[
-  {
-    "limit": 8,
-    "minimum_sold": 1000000,
-    "since": "2026-07-01"
-  }
-]New value: +[
+  {
+    "limit": 8,
+    "minimum_sold": 1000000,
+    "since": "2026-07-01"
+  },
+  {
+    "days": 30,
+    "limit": 10,
+    "min_amount": 10000000
+  }
+]
    • addedInput schema / properties / days
      Added value: +{
+  "description": "Look back this many days from `until` instead of supplying `since` (1-3650). An explicit `since` wins.",
+  "type": "number"
+}
    • addedInput schema / properties / min_amount
      Added value: +{
+  "description": "Alias for `minimum_sold`: minimum reported amount sold in USD.",
+  "type": "number"
+}
    • changedInput schema / properties / minimum_sold / description
      Previous value: -"Optional minimum reported amount sold in USD."New value: +"Only return offerings reporting at least this much sold, in USD. Also accepted as `min_amount`."
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive behavior, so the bar for additional disclosure is lower. The description adds meaningful context by identifying the source (official filing XML), the interpretive caveat that a Form D is self-reported and not proof of a closed round, and the warning that amendments must not be double-counted. This goes beyond the schema and annotations without contradicting them.

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 sentences, all substantive: the first identifies the resource and output, the second frames the data's reliability, and the third warns about amendment handling. No redundant phrasing, and the core purpose is front-loaded.

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 read-only list tool with a fully documented schema and an existing output schema, the description covers the key semantic quirks (self-reported data, amendment double-counting) that an agent must know to interpret results correctly. It does not enumerate sibling distinctions, but that gap is more about usage guidance than the completeness of the call context itself.

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%, with detailed descriptions for all 8 parameters including defaults, aliases, and ranges, so the baseline is 3. The description mentions fields like amount sold and industry in the output, which weakly reinforces the purpose of filters like minimum_sold and industry, but it does not add new parameter behavior beyond what the schema already provides.

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 clearly identifies the resource (recent SEC Form D exempt-offering notices), the ordering (newest first), and the enriched fields returned (offering amount, amount sold, investors, security types, industry, issuer, related persons). The 'recent' framing and self-reported caveat differentiate it from sibling tools like form_d_offering_detail or form_d_issuer_history.

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

Usage Guidelines2/5

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

The description provides no explicit when-to-use guidance or mention of when to choose a sibling tool instead. With eight form_d_* siblings, the agent must infer from 'recent' and 'notices' that this is the list/recent feed rather than detail, history, or amendment-chain tools. The amendment caveat implies filtering behavior but does not directly compare this tool to alternatives.

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

All Sec Form D toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation2/5

Many tools have overlapping purposes, e.g., ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded all route questions to data sources with minor differences. Form D tools and meta-tools (discover_tools, suggest_questions) further blur boundaries, making it hard for an agent to select the right tool.

Naming Consistency4/5

Most tools follow a consistent snake_case verb_noun pattern (e.g., resolve_entity, validate_claim, subscribe). However, there are minor deviations like bet_research and deep_research without clear verbs, and the ask_pipeworx variants use irregular suffixes.

Tool Count2/5

With 39 tools, the server is over-scoped, including many utility and meta-tools (remember, recall, forget, list_subscriptions) that inflate the count beyond the core domain (SEC Form D and data lookups). A more focused set of 10-15 tools would be more coherent.

Completeness4/5

The tool set covers a very broad range of data sources and actions, including SEC filings, prediction markets, entity profiling, and AI visibility. However, the completeness is uneven; for example, there are many Form D tools but few for other SEC forms, and some areas like weather or clinical trials are only accessible via ask_pipeworx.

Resources