Fintel Discovery — Financial Intelligence for AI Agents

Search FINRA BrokerCheck — Individuals

SearchBrokerCheck

Read-onlyIdempotent

    Search FINRA BrokerCheck for registered individual brokers and financial
    representatives by name. Returns CRD number, current firm, registration
    status, and whether the individual has any disclosures on record.

    Use this tool when:
    - You need to find the CRD number for a named advisor or rep
    - You want to verify registration status for a specific individual
    - You are enriching a rep record that is missing a CRD

    Geographic workflow: if you don't know the rep's name, first use
    SearchBrokersByPlace to discover firms in an area, then use
    SearchBrokerCheckFirm to find the firm's CRD, then use this tool
    to find individuals at that firm.

    Narrow results with the optional 'state' parameter (2-letter code).
    To get the full profile after finding a CRD, use GetBrokerCheckDetail.

    Source: FINRA BrokerCheck public API. No API key required.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`params`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds genuine context beyond that: the data source (FINRA BrokerCheck public API), that no API key is required, and the specific return fields. No contradiction with annotations.

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?

The description is longer than average but every section earns its place: core function, use cases, workflow routing, state hint, follow-up tool pointer, and source/no-auth note. It is front-loaded with the what-it-does sentence and uses bullet structure for scannability.

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?

For a read-only search tool with an output schema and a large sibling family, the description is complete: it explains what it returns, how it fits into the multi-step geographic workflow, when to use alternatives, and the authentication state. Nothing an agent needs to call it 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?

The description adds meaning for the two primary search params — name (search by name) and state ('Narrow results with the optional state parameter'). However, the tool exposes 12 nested parameters and the description is silent on most of them; it relies on the schema's per-parameter descriptions for the rest. Acceptable but not compensating beyond baseline.

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?

The description opens with a specific verb-resource pair ('Search FINRA BrokerCheck for registered individual brokers... by name') and states what the tool returns (CRD number, current firm, registration status, disclosures). The title adds 'Individuals' to distinguish from SearchBrokerCheckFirm, and the workflow section explicitly names the siblings it is not.

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?

There is an explicit 'Use this tool when' list (find CRD number, verify registration status, enrich a rep record) plus a geographic workflow that tells the agent to use SearchBrokersByPlace and SearchBrokerCheckFirm first when the name is unknown, and GetBrokerCheckDetail after. This is clear when/when-not guidance with named alternatives.

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

All Fintel Discovery — Financial Intelligence for AI Agents tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0

Disambiguation4/5

Most tools target a distinct resource and action, with clear separation between search and detail tools (e.g., SearchIAPDFirm vs GetIAPDFirmDetail, SearchBrokerCheck vs GetBrokerCheckDetail). A few pairs like SearchBrokerCheck and SearchBrokerCheckFirm could cause momentary confusion, but descriptions clarify individual vs firm scope.

Naming Consistency4/5

The dominant pattern is consistent: Search* for discovery, Get* for retrieval, with CamelCase throughout. Minor deviations like LookupTicker and MapInstrumentIds introduce different verbs, and SearchBrokerCheck does not explicitly signal 'individual' unlike SearchBrokerCheckFirm, but the overall convention remains predictable.

Tool Count2/5

With 32 tools, the surface is quite heavy and exceeds the 25+ threshold for 'too many.' While the financial intelligence domain is broad, several search/detail pairs and overlapping data-source tools could be consolidated to reduce cognitive load for agents.

Completeness4/5

The toolset covers major workflows well: 13F holdings, fund fee comparison, advisor due diligence, macro data, price history, options, and identifier mapping. Minor gaps exist, such as no standalone real-time quote tool, no news/sentiment data, and no direct CUSIP-to-company-name search, but these are workable around.

Resources

Need Help?