Skip to main content
Glama

Find placement agents

find_placement_agents
Read-onlyIdempotent

Find the broker-dealers and advisers that issuers paid to sell private offerings of one kind, from the Form D each issuer files (Item 12, sales compensation): by what the offering is ("real estate", or an industry group a Form D issuer ticks), the fund type (private equity, hedge, venture), the exemption (Rule 506(b) or 506(c)), the offering's size, its minimum investment, the year and a state the firm may solicit in. Or give like_offering, an offering's id from find_offerings, and the filters are taken from that offering. Returns how many firms match, and each firm with how many matching offerings named it, its newest ones with their size and terms, and which of a phone line and a mailbox it publishes. With include_contacts, it also returns each firm's own mailboxes and phone lines, using one credit from the account's monthly allowance for each firm opened. A firm here was named by the issuer as paid in connection with sales; that is not a claim that it raised the amount sold.

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

Input Schema

NameRequiredDescriptionDefault
pageNoWhich page of results, from 1.
ruleNoThe exemption the offering claims. 506c: Rule 506(c), general solicitation allowed, accredited investors only. 506b: Rule 506(b), no general solicitation.
sortNoThe order: offerings (the firms named on the most matching offerings first) or latest (the most recently named first).offerings
limitNoHow many firms to return, 1 to 50.
stateNoA state the firm may solicit in on the offering (the form's states of solicitation, or every state), as a two-letter code.
industryNoWhat the offerings are: "real estate" (the form's five real estate groups, tenant-in-common interests and real estate funds), or one industry group as the Form D prints it: 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.
firm_kindNoOnly firms of this kind.
fund_typeNoOnly offerings of pooled funds of this type, or of any in a list, as the Form D states it: "private-equity", "hedge", "venture", "other-fund".
since_yearNoOnly firms named on a notice filed in this year or later.
like_offeringNoAn offering's id from find_offerings: finds the firms paid on offerings like that one. Its industry (or fund type), its exemption, a size from a third of its size to three times it, and its issuer's state are used as the filters, and the result says which. A filter you also give takes its place.
include_contactsNoAlso return each firm's own mailboxes and phone lines in its row. Each firm whose contact is opened uses one credit from the account's monthly allowance, the same credits a person's contact uses; a firm with none 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 which contacts are on file either way (contacts_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.
max_minimum_investment_usdNoThe most the offering's minimum investment may be, in US dollars: 50000 finds offerings an investor can enter with $50,000 or less.

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 firm's own mailboxes and phone lines in its row. Each firm whose contact is opened uses one credit from the account's monthly allowance, the same credits a person's contact uses; a firm with none 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 which contacts are on file either way (contacts_on_file).",
      +  "type": "boolean"
      +}
    • removedInput schema / properties / show_contacts
      Removed value: -{
      -  "default": true,
      -  "description": "Each firm's own mailboxes and phone lines in its row, as its page lists them. On unless set to false. They cost no credit; people's own contacts are search_people.",
      -  "type": "boolean"
      -}
  2. Changed3 schema fields changed
    • addedInput schema / properties / fund_type
      Added value: +{
      +  "anyOf": [
      +    {
      +      "enum": [
      +        "private-equity",
      +        "hedge",
      +        "venture",
      +        "other-fund"
      +      ],
      +      "type": "string"
      +    },
      +    {
      +      "items": {
      +        "enum": [
      +          "private-equity",
      +          "hedge",
      +          "venture",
      +          "other-fund"
      +        ],
      +        "type": "string"
      +      },
      +      "maxItems": 4,
      +      "minItems": 1,
      +      "type": "array"
      +    }
      +  ],
      +  "description": "Only offerings of pooled funds of this type, or of any in a list, as the Form D states it: \"private-equity\", \"hedge\", \"venture\", \"other-fund\"."
      +}
    • addedInput schema / properties / like_offering
      Added value: +{
      +  "description": "An offering's id from find_offerings: finds the firms paid on offerings like that one. Its industry (or fund type), its exemption, a size from a third of its size to three times it, and its issuer's state are used as the filters, and the result says which. A filter you also give takes its place.",
      +  "pattern": "^fdo:[0-9-]{10,30}$",
      +  "type": "string"
      +}
    • addedInput schema / properties / show_contacts
      Added value: +{
      +  "default": true,
      +  "description": "Each firm's own mailboxes and phone lines in its row, as its page lists them. On unless set to false. They cost no credit; people's own contacts are search_people.",
      +  "type": "boolean"
      +}
  3. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare this a safe, idempotent read, and the description still adds material behavior: per-firm credit consumption from a monthly allowance, that firms with no contacts on file cost nothing and already-opened firms are free this month, and the semantic caveat that being named as paid is not evidence the firm raised the amount sold. This is exactly the kind of cost and interpretation 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 data source are front-loaded, and every clause carries filter or return information. It is dense as a single long paragraph, and the contact-credit caveat buried at the end would read better as its own sentence, but there is little padding.

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?

With 14 optional parameters and no output schema, the description compensates by spelling out the return shape: match count, each firm with its matching-offering count, newest offerings with size and terms, published phone/mailbox availability, and the contacts_on_file flag. Nothing an agent needs to call or interpret this correctly is missing.

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?

Schema coverage is 100%, so the baseline is 3; the description rises above it by summarizing the filter set in prose and explaining the like_offering override rule and how it derives industry, exemption, size band and issuer state. Most of that detail is duplicated in the schema, so it aids scanning more than it adds new meaning.

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?

States a specific verb and resource ('Find the broker-dealers and advisers that issuers paid to sell private offerings') plus the exact data source (Form D Item 12, sales compensation), which no sibling covers. An agent can tell this apart from find_offerings, find_firms or search_firms without opening a 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 explicit routing via like_offering ('an offering's id from find_offerings') and an explicit conditional instruction for include_contacts ('Use it only when the person asks for contact details'). It does not contrast itself against the other firm-search siblings, so it stops short of full when/when-not coverage.

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