Skip to main content
Glama

AdvisorIQ

by com.advisoriq
OverviewDiscussionsAdmin

One RIA firm's profile

get_ria_firm
Read-onlyIdempotent

One independent wealth management RIA's figures from its Form ADV, by CRD number: registration and status, location, website, regulatory assets under management (discretionary and not), accounts, clients and client types, employees and adviser representatives, fee types, services, affiliations, custody, whether it reported disclosures, growth over 1, 3 and 5 years, its national and state ranks among independent RIAs, and its yearly history from the SEC's files. A broker-dealer affiliated wealth firm (a wirehouse, a broker-dealer's advisory arm, a bank's) is returned only with include_bd_affiliated, ranked among all wealth firms. Asset managers and other firms outside wealth management are not in the directory. One firm per call; find the CRD with search_ria_firms.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
crdYesThe firm's Organization CRD number, or its AdvisorIQ page URL
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
Behavior4/5

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

Annotations already cover readOnly/idempotent/non-destructive, so the bar is lower. The description nonetheless adds meaningful behavior: which firms are silently out of scope, that non-independent firms require a flag and are then ranked differently, and what the response contains. It stops short of describing error behavior when a CRD is outside the directory.

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 core purpose and constraint, then scope caveats. The field enumeration is a long run-on list, but every item carries selection value and nothing is redundant with the schema.

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 compensates by enumerating the returned data comprehensively, and it closes the remaining gaps: one firm per call, how to find the CRD, and which firm classes fall outside the directory.

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 goes beyond it by clarifying that crd accepts either a CRD number or an AdvisorIQ page URL, and that include_bd_affiliated changes both coverage and ranking population — semantics the schema only states tersely.

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+resource: one independent RIA firm's Form ADV figures, keyed by CRD number. It enumerates the exact data domains returned (registration, AUM, clients, ranks, yearly history), so an agent knows precisely what this tool yields versus siblings like ria_rankings or ria_market_stats.

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?

Explicitly states the one-firm-per-call constraint and routes the agent to search_ria_firms to obtain the CRD. It also defines scope boundaries: BD-affiliated firms only appear with include_bd_affiliated, and asset managers/other firms are excluded from the directory entirely.

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