Skip to main content
Glama

AdvisorIQ

by com.advisoriq
OverviewDiscussionsAdmin

Find an RIA firm

search_ria_firms
Read-onlyIdempotent

Find independent wealth management RIAs (SEC or state registered) in AdvisorIQ's directory by part of the firm's name, its CRD number or SEC 801- number, or its main office city, optionally within one state. Returns at most 25 firms, best name matches first and then by assets, each with CRD, city, state, registration, regulatory assets under management and its AdvisorIQ page. Set include_bd_affiliated to also search broker-dealer affiliated wealth firms such as the wirehouses. Asset managers, private fund managers and pension consultants are not in the directory. Use it to get the CRD for get_ria_firm. Firm-level data only: it never returns individual advisers.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesPart of the firm name, a CRD number, an SEC number (801-12345), or a city
stateNoOptional: two-letter code or name of the firm's state, e.g. TX or Texas
include_bd_affiliatedNoOptional, default false: also cover broker-dealer affiliated wealth firms (wirehouses, broker-dealers and their advisory arms, banks), which AdvisorIQ lists apart from independent RIAs

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / include_bd_affiliated
      Added value: +{
+  "description": "Optional, default false: also cover broker-dealer affiliated wealth firms (wirehouses, broker-dealers and their advisory arms, banks), which AdvisorIQ lists apart from independent RIAs",
+  "type": "boolean"
+}
  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 establish readOnly/idempotent/non-destructive, and the description layers on genuinely non-derivable behavior: a hard cap of 25 results, the ranking order (best name match, then assets), the fields returned per firm, and the guarantee that individual advisers are never returned. This is exactly the extra context annotations cannot supply.

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 action and primary lookup keys, and each subsequent sentence (return shape, exclusion list, sibling handoff) carries distinct information. It is dense but slightly long for a single paragraph; no sentence is pure filler, though the result-field list borders on redundant with what a consumer can discover.

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 must, and does, explain the return payload (cap, ordering, per-firm fields and page link), plus scope limitations and the CRD handoff path. Nothing an agent needs to call this correctly 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 description coverage is 100%, so all three parameters are already documented (query key types, state, include_bd_affiliated default). The description largely restates those keys, adding only examples like 'wirehouses' and the 'within one state' phrasing, which the schema already implies.

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 (find) plus resource (independent wealth-management RIAs in AdvisorIQ's directory) and enumerates the accepted lookup keys. It also explicitly demarcates itself from get_ria_firm (lookup by CRD) and from sibling search tools, so an agent can route without opening schemas.

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?

Gives explicit when-to-use ('Use it to get the CRD for get_ria_firm'), a conditional toggle for when to include broker-dealer affiliated firms, and negative scope ('Asset managers, private fund managers and pension consultants are not in the directory'). Nothing about selection is left to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All AdvisorIQ toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources