Skip to main content
Glama

Get a firm's brochure

get_brochure
Read-onlyIdempotent

What an investment adviser's Form ADV Part 2 brochure states, read from the brochure it files with the SEC: the assets it manages, its fees and minimums, its owners, affiliates, custodians and brokers, its services, strategies and kinds of client, its referral arrangements, conflicts of interest, disciplinary information, custody, discretion, voting and review practices, the risks it names, the funds it names with each one's strategy, management fee, performance fee and minimum investment, and the people it describes with their schools, credentials and earlier roles. Each row gives the brochure's own words and the page they are on, and a stated value only when it is on that page. Use it for an adviser's fee schedule, account minimum, who owns it, which custodian it uses, a fund's terms, or what it discloses. One part alone with part. Broker-dealers and exempt reporting advisers file no brochure.

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": {
      "firm_id": "<firm_id>"
    },
    "name": "get_brochure"
  }
}

Input Schema

NameRequiredDescriptionDefault
partNoOne part of the brochure alone, with up to 200 rows: assets (assets it manages), fees (fees), minimums (minimums), owners (owners), affiliates (affiliates), custodians (custodians and brokers), services (services), strategies (strategies), clients (clients), referrals (referral arrangements), conflicts (conflicts of interest), disciplinary (disciplinary information), practices (custody, discretion, voting and review), risks (risks it names), about (in its own words), funds (the funds it names, with their terms), people (the people it describes). Leave it out for every part, 25 rows each.
firm_idYesThe firm's id from search_firms or get_firm (for example ria-158763), or its corridome.com address.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds real behavior beyond that: rows return the brochure's own words plus page numbers, a value is stated only when it appears on that page, and row volume differs (up to 200 for a single part vs 25 each when omitted). It says nothing about truncation handling when the 200-row cap is hit.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core statement is front-loaded well, but the opening sentence is a ~120-word run-on enumerating fields that the part enum already documents, so it is partly redundant. The shorter trailing sentences (use cases, part guidance, entity exclusion) are efficient; the field catalogue could be trimmed without losing selection signal.

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 no output schema, the description correctly carries the burden of explaining return shape (verbatim text plus page per row, values only when stated on that page) and notes which entity types yield nothing. The remaining gap is what happens when the 200-row single-part cap is reached — whether results truncate or another call is needed.

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% and the part enum already lists every value with its gloss, so the description mostly restates it. The one addition is the 'One part alone with part' / 'Leave it out for every part, 25 rows each' contrast, which clarifies the trade-off between the two modes but is largely repeated from the schema text.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb (read) and resource (an adviser's Form ADV Part 2 brochure as filed with the SEC), and enumerates the content domains covered: assets, fees, owners, custodians, conflicts, funds, people. An agent knows exactly what comes back. It stops short of naming a sibling to contrast with (e.g. get_firm), so the boundary with adjacent lookups is only implied by the word 'brochure'.

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 concrete when-to-use cases ('an adviser's fee schedule, account minimum, who owns it, which custodian it uses, a fund's terms') and an explicit exclusion: 'Broker-dealers and exempt reporting advisers file no brochure', which prevents wasted calls on ineligible entity types. It does not name an alternative tool to use instead when the entity has no brochure, leaving that inference to the agent.

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