Skip to main content
Glama

Brokercheck Search Firm

brokercheck_search_firm
Read-onlyIdempotent

Search brokerage / broker-dealer firms by name via FINRA BrokerCheck. Returns matching firms with CRD number, SEC number, registration scope, a disclosure flag (has_disclosures, the firm has reported regulatory/disciplinary events), and branch count. Per-name lookup only.

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": "Merrill Lynch"
    },
    "name": "brokercheck_search_firm"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax firms to return (1-50, default 10).
queryYesFirm name to search (e.g. "Merrill Lynch", "Edward Jones").

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds value beyond that by disclosing the return payload (CRD number, SEC number, registration scope, branch count) and explaining that has_disclosures flags reported regulatory/disciplinary events, though it says nothing about pagination or result ordering.

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?

Purpose and scope are front-loaded and the enumerated return fields earn their place since there is no output schema. The single long sentence packs in many clauses and could be split, but there is no 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?

For a two-parameter read-only lookup with no output schema, the description covers input intent (per-name lookup), the identity of the backend (FINRA BrokerCheck), and the shape of the response including the meaning of the disclosure flag. Nothing essential to calling 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?

Schema coverage is 100% and both parameters (query, limit) are already described in the schema, so the baseline is 3. The description reinforces the query format with example-style framing ("by name") but adds no syntax, normalization, or partial-match behavior beyond the schema.

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 names a specific verb and resource ("Search brokerage / broker-dealer firms by name via FINRA BrokerCheck") and scopes it ("Per-name lookup only"), which distinguishes it from brokercheck_search_individual and generic registers without ambiguity.

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 closing constraint "Per-name lookup only" tells the agent this cannot be used to browse or list all firms, which is real usage guidance. It stops short of naming a sibling alternative for bulk or discovery needs, so it is clear context but not full when/when-not routing.

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.