Skip to main content
Glama

Brokercheck Search Individual

brokercheck_search_individual
Read-onlyIdempotent

Search individual stockbrokers and investment-adviser representatives by name via FINRA BrokerCheck, the regulator-published registry investors use for due diligence and investor-protection background checks. Returns matching individuals with CRD number, name, registration scope (active/inactive), a disclosure flag (has_disclosures, whether the person has any reported disciplinary/regulatory/customer-dispute event), and current employing firm(s). Use brokercheck_individual_detail with a returned CRD to see the actual disclosure events. Per-name lookup only, not for bulk enumeration.

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": {
      "query": "John Smith"
    },
    "name": "brokercheck_search_individual"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax individuals to return (1-50, default 10).
queryYesIndividual name to search (e.g. "John Smith").

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world. The description adds real meaning beyond that: it explains what the has_disclosures flag signifies (any disciplinary/regulatory/customer-dispute event) and that the registry is regulator-published, which affects trust in results. It does not cover result ordering, rate limits, or auth, which keeps it below a 5.

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 source, then returns, then routing; no redundant sentences. The qualifying clause about investor due diligence is slightly promotional but still gives useful trust context for the source.

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 carries the return-value burden and does so: it enumerates the fields returned and explains the one non-obvious flag. Combined with the routing instruction to the detail tool, an agent has everything needed to call it and interpret the response.

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%, with both 'query' and 'limit' documented in the schema including the range and default. The description adds only that lookup is by name rather than CRD, so it does not need to compensate further; baseline 3 applies.

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 ('Search individual stockbrokers and investment-adviser representatives by name') plus the data source (FINRA BrokerCheck). It also outlines the exact fields returned (CRD, name, registration scope, disclosure flag, employing firms), so the agent knows what it is getting without consulting a 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?

Gives an explicit next step ('Use brokercheck_individual_detail with a returned CRD to see the actual disclosure events') and an explicit exclusion ('Per-name lookup only, not for bulk enumeration'). Both when-to-use and when-not-to-use are covered, and it routes to the correct sibling.

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.