Fintel Discovery — Financial Intelligence for AI Agents

Get SEC IAPD Individual Detail

GetIAPDIndividualDetail

Read-onlyIdempotent

    Retrieve the full SEC IAPD profile for one individual investment advisor
    representative using their CRD number. Returns complete registration history,
    exam qualifications, employment history, and any disclosures.

    Use this tool when:
    - You have a CRD (from SearchIAPDIndividual) and need the full profile
    - You need an advisor's complete Form ADV Part 2B equivalent data
    - You are performing deep due diligence on an individual IAR

    Source: SEC IAPD public API (api.adviserinfo.sec.gov). 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.3/5.0

Behavior4/5

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

Annotations already indicate readOnly, idempotent, and non-destructive behavior. The description adds meaningful behavioral context by specifying the returned content: complete registration history, exam qualifications, employment history, and disclosures, plus the external SEC API source and lack of API key requirement.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with a concise opening line, scannable use-case bullets, and a short source note. Every sentence serves a purpose and no filler or repetition is present.

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?

Given the tool's complexity, the presence of an output schema, and annotations covering safety, the description provides sufficient context: the input source, what data will be returned, when to use it, and the external API source. No critical calling information 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 emphasizes the essential CRD parameter and where to obtain it, which adds modest semantic value. However, with schema description coverage reported as 0% at the top level, the description does not compensate for the many optional parameters like filters, resumability, or display fields, leaving that burden to the nested schema descriptions.

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 clearly identifies the action ('Retrieve the full SEC IAPD profile'), the specific resource ('one individual investment advisor representative'), and the key identifier ('CRD number'). It also distinguishes itself from sibling tools like GetIAPDFirmDetail and SearchIAPDIndividual by targeting full individual-level detail.

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 tool provides explicit use-case bullets, such as having a CRD from SearchIAPDIndividual, needing Form ADV Part 2B-equivalent data, and performing deep due diligence. It does not explicitly state when not to use this tool or mention alternatives like GetIAPDFirmDetail, but the stated conditions are clear and actionable.

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?