Skip to main content
Glama

Advisor firm changes as registration dates

search_ria_advisor_moves
Read-onlyIdempotent

Advisors who left one firm and registered at another: the person, from and to firms with class, the registration end and begin dates, the gap, and the move type (WIREHOUSE_TO_RIA, IBD_TO_RIA, RIA_TO_RIA, ...). Filter by from firm, to firm, advisor, move type and date window, and with a firm by state: state=CA with to_dfx_id is moves into the firm in CA, with from_dfx_id moves out of it in CA (a move is in a state when any branch on the advisor's registration at the destination firm, or the origin firm when only from is given, is there; state_filter.basis says so). Bulk corporate re-registrations (an acquirer re-registering a roster on one day, 99,737 rows) are EXCLUDED unless include_bulk; departures with no registered destination are excluded unless include_departures. A move is two dates on IAPD, never a statement about why. Not a prediction of who will move. ACCESS: without a paid DFX plan on the vertical, a list returns its first 5 rows in full and a count of the rest by type (locked.count, locked.by_type), never the rows; a record names its subject and the first 3 related names per section; contact values (email, phone, profile URLs) and decision-maker names are never returned, only their types and counts. Every answer says what it withheld in entitlement and locked. Full access: DFX Intelligence, 7 days free at https://dfxintel.com/data-factory/plans.

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": "search_ria_advisor_moves"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
sinceNoISO date; registration ended on or after.
stateNoTwo-letter US state code (USPS, DC and territories included). Needs from_dfx_id or to_dfx_id: the advisor's branch at the destination firm (moves in) or, with only from_dfx_id, at the origin firm (moves out) decides.
untilNoISO date.
cursorNonext_cursor from a previous page of this tool, unchanged.
move_typeNo
to_dfx_idNoAn RIA graph id of the form dfx:ria:<uuid> (from search_ria, resolve_name or search_entities), or the firm's CRD number as a string.
from_dfx_idNoAn RIA graph id of the form dfx:ria:<uuid> (from search_ria, resolve_name or search_entities), or the firm's CRD number as a string.
include_bulkNo
advisor_dfx_idNoA dfx:ria: advisor id or an individual CRD.
include_departuresNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / state
      Added value: +{
      +  "description": "Two-letter US state code (USPS, DC and territories included). Needs from_dfx_id or to_dfx_id: the advisor's branch at the destination firm (moves in) or, with only from_dfx_id, at the origin firm (moves out) decides.",
      +  "type": "string"
      +}
  2. Added

TDQS

A4.3/5.0
Behavior5/5

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

Goes well past the readOnly/idempotent annotations: it discloses that bulk corporate re-registrations (99,737 rows) and destination-less departures are excluded by default, and precisely what an unentitled caller receives (first 5 rows, locked.count/locked.by_type, truncated related names, contact values never returned). Documenting the `entitlement` and `locked` output keys is exactly the kind of behavioral 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?

Core purpose is front-loaded in the first sentence, followed by filtering, exclusions, definitional caveats and access terms in a logical order. It is dense and long for one description, and the state-branch clause is a single run-on sentence that takes effort to parse, but no sentence is filler.

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?

Eleven parameters, no output schema, no required fields — the description carries the definitional, exclusionary and entitlement burden and does so, including naming the response keys that signal withheld data. An agent has enough to decide, call and interpret the result correctly.

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 64%; the description compensates for the weakest parts by explaining the state + to_dfx_id/from_dfx_id interaction, the state_filter.basis field, and the meaning of include_bulk and include_departures. The move_type enum values are echoed as examples, though since/until/cursor/limit semantics are left to the schema.

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?

Opens with a specific verb+resource: advisors who left one firm and re-registered at another, and enumerates the returned fields (person, from/to firms with class, begin/end dates, gap, move type). The closing caveats ('never a statement about why', 'Not a prediction of who will move') implicitly separate it from search_ria_move_indicators, but no sibling is named outright.

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?

Clear guidance on how to filter (from firm, to firm, advisor, move type, date window) and on the non-obvious prerequisite that state requires from_dfx_id or to_dfx_id to disambiguate in vs. out. It also states defaults for include_bulk and include_departures, but never points to an alternative tool when this one is the wrong choice.

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.