Skip to main content
Glama

Find new offerings

find_offerings
Read-onlyIdempotent

Find Form D offerings by the day their first notice was filed, in one call: new raises since a date, narrowed by whether their notices name anyone paid for sales (sales_pay "none" finds offerings that name no broker-dealer or placement agent so far), by what they are (real estate or an industry group, a fund type), the exemption, the size, the minimum investment and the issuer's state. Returns how many match, and each offering with its issuer, place, terms, first filing day, and who is behind it: who signed the notice, the people it names (executive officers first), the firms it paid, and whether the notice files the issuer's phone. With include_contacts, it also returns that phone, using one credit from the account's monthly allowance for each offering opened. Use it for a list of issuers who are raising now. Then, for the firms paid on offerings like one of them, find_placement_agents with like_offering.

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_offerings"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoWhich page of results, from 1.
ruleNoThe exemption claimed. 506c: Rule 506(c), general solicitation allowed, accredited investors only. 506b: Rule 506(b), no general solicitation.
sortNoThe order: newest (the latest first notice first) or largest (the largest offering first).newest
limitNoHow many offerings to return, 1 to 50.
stateNoThe issuer's state, or a list of states, as two-letter codes: ["TX", "OR"].
industryNoWhat the offering is: "real estate" (the form's five real estate groups, tenant-in-common interests and real estate funds), an industry group as the form prints it, or a list of them: Residential, Commercial, Construction, REITS and Finance, Other Real Estate, Pooled Investment Fund, Oil and Gas, Other Energy, Biotechnology, Pharmaceuticals, Other Health Care, Hospitals and Physicians, Other Technology, Computers, Telecommunications, Commercial Banking, Insurance, Investing, Investment Banking, Other Banking and Financial Services, Business Services, Manufacturing, Retailing, Restaurants, Agriculture, Lodging and Conventions, Other.
fund_typeNoOnly pooled funds of this type, or of any in a list, as the form states it: "private-equity", "hedge", "venture", "other-fund".
sales_payNoWhether the offering's notices name anyone paid in connection with its sales (Form D Item 12): "none" finds offerings that name nobody so far, "named" those that name a firm.any
filed_sinceNoFirst notices filed on or after this day, as YYYY-MM-DD. Left out, the last thirty days. One search reads 366 days at most.
show_peopleNoWho is behind each offering, in its row: who signed the notice, the people it names (executive officers first), the organizations among them, and the firms it paid. On unless set to false.
filed_beforeNoAnd before this day, as YYYY-MM-DD.
include_contactsNoAlso return each issuer's phone as its notice files it. Each offering whose phone is opened uses one credit from the account's monthly allowance, the same credits a person's contact uses; an offering with no phone on file costs nothing, and one already opened this month is free. Use it only when the person asks for contact details, and say how many credits it used. Every row says whether a phone is on file either way (phone_on_file).
max_offering_usdNoThe largest total offering size, in US dollars.
min_offering_usdNoThe smallest total offering size, in US dollars. An offering of indefinite size matches no size filter.
first_notice_onlyNoOnly offerings with one notice on file: a new offering. Set false to include offerings that have been amended since.
max_minimum_investment_usdNoThe most the minimum investment may be, in US dollars.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / include_contacts
      Added value: +{
      +  "default": false,
      +  "description": "Also return each issuer's phone as its notice files it. Each offering whose phone is opened uses one credit from the account's monthly allowance, the same credits a person's contact uses; an offering with no phone on file costs nothing, and one already opened this month is free. Use it only when the person asks for contact details, and say how many credits it used. Every row says whether a phone is on file either way (phone_on_file).",
      +  "type": "boolean"
      +}
    • changedInput schema / properties / show_people / description
      Previous value: -"Who is behind each offering, in its row: who signed the notice, the people it names (executive officers first), the issuer's phone, and the firms it paid. On unless set to false."New value: +"Who is behind each offering, in its row: who signed the notice, the people it names (executive officers first), the organizations among them, and the firms it paid. On unless set to false."
  2. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already establish that this is a safe, idempotent, closed-world read, and the description goes well beyond them by disclosing the credit cost model for include_contacts (one credit per offering opened, free when no phone is on file or already opened this month, and an instruction to report credits used). It also states the 366-day search ceiling and the thirty-day default window, which materially affect how the agent should call it.

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?

Front-loaded with purpose and then organized roughly as filters, returns, and next-step routing, so it is easy to navigate. It is dense, however, and the first sentence is a long run-on enumeration of filters that would read better as a short list of clauses.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a sixteen-parameter tool with no output schema, so the description must carry the return shape itself, and it does: a match count plus each offering with issuer, place, terms, first filing day, signer, named people in officer-first order, firms paid, and a phone_on_file flag. Nothing an agent needs in order to call it or interpret the result is left implicit.

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 real business meaning on top: it explains that sales_pay "none" means the notices name no broker-dealer or placement agent so far, and it frames industry as spanning real estate groups, industry groups, and fund types. The remaining filters (size, state, exemption, page/limit) are restated from the schema rather than illuminated.

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 plus resource and scope: "Find Form D offerings by the day their first notice was filed, in one call." It immediately tells the agent what the result set is (new raises since a date) and separates itself from the follow-up tool find_placement_agents, so the agent can pick correctly 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?

Gives an explicit use case ("Use it for a list of issuers who are raising now") and routes to a named alternative for the follow-on question about firms paid on similar offerings. It also constrains include_contacts to cases where contact details are actually requested. What is missing is any when-not guidance versus the other discovery siblings such as find_companies or find_buyers.

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