Skip to main content
Glama

Adv Firm Profile

adv_firm_profile
Read-onlyIdempotent

Get the SEC Form ADV / IAPD profile for an investment-adviser firm by its CRD number (the firm_source_id / CRD returned by adv_search_firm). Returns basic firm info, registration status, SEC number, notice-filing jurisdictions, disclosure flag, Form ADV Part 2 brochure list, and direct links to the full Form ADV report PDF. Also returns regulatory_aum: Form ADV Part 1A Item 5.F regulatory assets under management (discretionary, non-discretionary, total, in USD), account counts and non-US-client AUM, from the SEC Division of Investment Management monthly adviser release, with its data_as_of. Present for SEC-registered advisers only (state-registered and exempt reporting advisers file no 5.F in that release; the field says so). Disciplinary narratives still live in the linked Form ADV PDF.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "crd": "107342"
    },
    "name": "adv_firm_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
crdYesFirm CRD number (a.k.a. firm_source_id), digits only. Never guess a CRD from a firm name: call adv_search_firm with the name first and use the CRD it returns.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / crd / description
      Previous value: -"Firm CRD number (a.k.a. firm_source_id), e.g. \"107342\" for Fisher Investments."New value: +"Firm CRD number (a.k.a. firm_source_id), digits only. Never guess a CRD from a firm name: call adv_search_firm with the name first and use the CRD it returns."
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds substantive behavior: the exact field set returned, the provenance and freshness of regulatory_aum (SEC Division of Investment Management monthly release, with data_as_of), the conditional presence of that field, and the explicit note that disciplinary narratives are only in the linked Form ADV PDF – preventing a false 'no disclosures' conclusion.

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 the verb and key, then the return inventory, then the regulatory_aum caveat and the PDF pointer. It is dense rather than padded, though the return-field enumeration is long enough that the important caveat about missing disciplinary narratives sits at the very end.

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 no output schema, the description enumerates the return payload itself, including taxonomy of the regulatory_aum sub-fields (discretionary, non-discretionary, total, account counts, non-US-client AUM) and its as-of date. Coverage limits and where excluded data lives are both stated, so nothing an agent needs to interpret the result is missing.

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 single parameter's schema description already carries the 'never guess a CRD' warning, so the schema does the heavy lifting. The description adds only the alias 'firm_source_id / CRD returned by adv_search_firm', which is a marginal but real clarification of provenance. Baseline 3 is appropriate here.

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 ('Get the SEC Form ADV / IAPD profile for an investment-adviser firm by its CRD number') and immediately scopes it against the sibling by tying the key to what adv_search_firm returns. An agent can distinguish this lookup from adv_search_firm without opening either schema.

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

Usage Guidelines5/5

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

The parameter guidance and description both route the agent: 'Never guess a CRD from a firm name: call adv_search_firm with the name first and use the CRD it returns' names the alternative and the condition that selects it. The description also clarifies the boundary case where regulatory_aum is absent (state-registered and exempt reporting advisers), which implicitly tells the agent this tool still works for them but with less data.

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.