Skip to main content
Glama

Brokercheck Individual Detail

brokercheck_individual_detail
Read-onlyIdempotent

Get the full FINRA BrokerCheck profile for one individual broker/adviser rep by CRD number (from brokercheck_search_individual). Returns employment history (current + previous firms) and, when present, the actual disclosure EVENTS, each with event date, disclosure type (e.g. Customer Dispute, Regulatory, Criminal, Financial, Termination), resolution status, and the disclosure detail (allegation/disposition). This is the "is this broker clean, and if not what happened" tool.

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": "5998211"
    },
    "name": "brokercheck_individual_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
crdYesIndividual CRD number (a.k.a. ind_source_id), returned by brokercheck_search_individual.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly=true, idempotent=true, destructive=false and openWorld=true, so the safety profile is covered. The description adds real behavioral value beyond that: it discloses the return contents (employment history current + previous, and disclosure events only 'when present'), the per-event fields, and the caveat that disclosures may be absent. It does not mention rate limits, empty-result behavior for an unknown CRD, or pagination, which keeps it short of 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 identifier, then the return contents in priority order, with the payload enumeration kept tight. The closing gloss 'is this broker clean, and if not what happened' adds a decision-oriented frame but is mildly redundant with the preceding sentence.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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 burden of describing returns, and it does so concretely (employment history, event date, disclosure type with examples, resolution status, allegation/disposition). For a one-parameter lookup this is nearly sufficient; only error/empty-result handling and any result-size limits are unaddressed.

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?

With a single parameter at 100% schema coverage, the schema already documents crd as the Individual CRD number (a.k.a. ind_source_id). The description only echoes the provenance (returned by brokercheck_search_individual), adding marginal meaning beyond the schema, so the 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: get the full FINRA BrokerCheck profile for one individual by CRD number. It explicitly routes to the sibling that produces that CRD (brokercheck_search_individual) and enumerates what the profile contains, so an agent can distinguish it from brokercheck_search_individual 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 Guidelines4/5

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

The parenthetical '(from brokercheck_search_individual)' establishes the intended search-then-detail workflow and implies which tool to use first. It does not state exclusions (e.g. use brokercheck_search_firm for firms) explicitly, so the contrast with the firm-level tool is left to be inferred from the resource name.

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.