Skip to main content
Glama

Ariadne Nexus Institutional Quantitative Engine

SEC Form X-17A-5 Net Capital, 13F-HR & FINRA SRO Broker-Dealer Forensics

audit_broker_dealer_forensics
Read-onlyIdempotent

Synthesizes structured broker-dealer counterparty and prime-clearing forensics combining SEC Form X-17A-5 (FOCUS Report) balance sheet and Rule 15c3-1 net capital cushion multiples, SEC Form 13F-HR institutional equity/option book telemetry, FINRA BrokerCheck SRO enforcement dockets, and SHA-256 OFAC sanctions Merkle attestations by CIK, FINRA CRD, or entity name. Use when: auditing a registered broker-dealer, quantitative market maker, or clearing counterparty (e.g., HRT Financial LP CIK 0001475597 / CRD 152144, HRT Execution Services LLC CIK 0001263128 / CRD 128491, or any SEC-filing broker-dealer CIK) for Rule 15c3-1 excess net capital, repo leverage, 13F concentration, or SRO regulatory history. Do not use when: screening a non-broker-dealer entity solely against OFAC SDN sanctions (use screen_ofac_entity instead) or computing corporate issuer Beneish M-Score whistleblower bounties (use generate_sec_tcr_bounty_dossier instead). Behavior: Read-only, deterministic forensic synthesis ($2.50 USD per call via HTTP header x-api-key or x-payment-token; returns an x402/MPP paymentChallenge without charging if credentials are omitted).

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

Input Schema

NameRequiredDescriptionDefault
cikNo10-digit SEC Central Index Key (CIK) of the registered broker-dealer or institutional investment manager (e.g., "0001475597" for HRT Financial LP or "0001263128" for HRT Execution Services LLC).0001475597
crdNoOptional FINRA BrokerCheck Central Registration Depository (CRD) number (e.g., "152144" or "128491").
entity_nameNoOptional legal or common name of the broker-dealer firm used when CIK or CRD is omitted (e.g., "Hudson River Trading", "HRT Financial LP").
top_holdings_limitNoMaximum number of ranked SEC Form 13F-HR holdings to return between 1 and 50 (default: 10).
include_sro_docketsNoWhether to include itemized FINRA and exchange SRO AWC/consent enforcement dockets (default: true).

Output Schema

NameRequiredDescriptionDefault
toolYesExecuted MCP tool identifier ("audit_broker_dealer_forensics").
receiptNoCryptographic payment or API key settlement receipt ID.
entity_profileYesResolved broker-dealer CIK, CRD, LEI, auditor, credit ratings, and prime brokers.
ofac_sanctions_attestationYesOFAC SDN screening status and SHA-256 Merkle proof.
finra_sro_enforcement_matrixNoFINRA BrokerCheck SRO disclosure summary and itemized enforcement dockets.
form_13f_institutional_telemetryNoSEC Form 13F-HR equity, put, and call book summary plus ranked holdings.
focus_x17a5_net_capital_forensicsNoSEC Form X-17A-5 balance sheet, repo leverage, and Rule 15c3-1 net capital cushion.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already establish readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, yet the description still adds material context: deterministic synthesis, a $2.50 per-call charge, credential mechanisms via x-api-key or x-payment-token, and the x402/MPP paymentChallenge returned without charging when credentials are absent. That payment/auth behavior is not derivable from any structured field. It stops short of a 5 only because it says nothing about latency, rate limits, or what happens on failed CIK resolution.

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 labeled 'Use when', 'Do not use when', and 'Behavior' segments make it scannable and front-load the core purpose. The opening sentence is a very dense run-on packed with domain jargon, and the inline worked examples (CIK/CRD pairs) are long, though they do serve as copyable invocation patterns.

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 an output schema present, the description needn't explain return values, and it covers everything else an agent needs: purpose, routing alternatives, auth/payment mechanics, and concrete identifier examples. For a five-parameter read-only forensic tool, nothing material is left ambiguous.

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 description coverage is 100%, so every parameter is already documented and the baseline is a 3. The description adds one useful nuance by framing the lookup as an alternative-key disjunction ('by CIK, FINRA CRD, or entity name'), but it does not elaborate on precedence when multiple keys are supplied, nor on how top_holdings_limit or include_sro_dockets affect output. Marginal value 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 opens with a specific verb ('Synthesizes') and enumerates the exact resources joined: SEC Form X-17A-5 FOCUS Report net capital, Form 13F-HR holdings, FINRA BrokerCheck dockets, and OFAC Merkle attestations. An agent can tell precisely what this produces and how it differs from siblings like screen_ofac_entity or synthesize_regulatory_docket.

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?

It gives explicit 'Use when' criteria (auditing a registered broker-dealer, market maker, or clearing counterparty for Rule 15c3-1 excess capital, repo leverage, 13F concentration, or SRO history) and explicit 'Do not use when' exclusions that name the correct alternative tool for each case. Both the positive and negative routing conditions are stated rather than inferred.

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.