Skip to main content
Glama

BRAINIAC SEC Form D Exempt Offering Search

Search SEC Form D exempt-offering notices

public-filings_sec-form-d-search
Read-onlyIdempotent

Find Form D and D/A notices of exempt offerings by issuer name or CIK in the vendored SEC Form D quarterly data sets (2025Q4 to 2026Q3) and return the offering fields as filed: exemptions, amounts, first sale date, and amendment link. Price $0.03 USDC. POST /api/v1/public-filings/sec-form-d-search. An unpaid call returns the x402 payment terms and does not run.

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": "public-filings_sec-form-d-search"
  }
}

Input Schema

NameRequiredDescriptionDefault
cikNocik, string. Optional.
limitNolimit, integer, from 1 to 50. Required.
issuerNameNoissuerName, string, length 2 to 200. Optional.
filingDateToNofilingDateTo, string, date. Optional.
filingDateFromNofilingDateFrom, string, date. Optional.
submissionTypeNosubmissionType, string, one of D, D/A. Optional.

Output Schema

NameRequiredDescriptionDefault
resultsNoresults. Array.
sourcesNosources. Array.
coverageNocoverage. Object.
limitationsNolimitations. Array.
totalMatchesNototalMatches. Number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the readOnly/idempotent/openWorld annotations, the description discloses the hard dataset boundary (2025Q4–2026Q3), the fields returned as filed, the price ($0.03 USDC), the POST endpoint, and the crucial failure mode that unauthenticated calls do not run and instead return payment terms. That is exactly the behavioral context annotations cannot carry.

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?

Purpose and scope are front-loaded in the opening sentence, followed by pricing, endpoint, and payment behavior. The first sentence is dense and carries somewhat different kinds of information, but no sentence is wasted.

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 an output schema present, the description needn't explain return shape, yet it still names the key offerings fields. Coverage of data vintage, pricing, and payment gating is strong; minor gaps remain around result ordering and whether cik and issuerName combine as AND or OR, which matters for a multi-filter search 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 the schema already documents all six parameters including their patterns and limits. The description adds only the semantic pairing of issuer name/CIK with the returned offering fields (exemptions, amounts, first sale date, amendment link); it says nothing about how multiple filters combine or what `limit` and `submissionType` do in practice.

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 ('Find'), a specific resource ('Form D and D/A notices of exempt offerings'), the exact data scope ('vendored SEC Form D quarterly data sets (2025Q4 to 2026Q3)'), and the lookup keys (issuer name or CIK). An agent knows precisely what this tool retrieves without opening 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 Guidelines4/5

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

It gives clear query context — search by issuer name or CIK within a bounded quarterly dataset — plus the operational rule that an unpaid call only returns x402 payment terms and does not execute the search. There is no explicit when-not guidance, but no sibling alternatives exist to route against.

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