SiteCheck Crypto & Finance

Investment adviser firm record from the SEC IAPD by CRD

finance_sec_investment_adviser

Read-only

Investment adviser firm record from the SEC IAPD (Form ADV) by CRD number or firm name: legal and other names, adviser status, SEC file number, latest Form ADV filing date and PDF link, office address, SEC / state / exempt-reporting registration flags, registration history, state notice filings and brochure list, plus the IAPD page. Related tools on this server, for a different need: finance_sec_iapd when you need to search the SEC Investment Adviser Public Disclosure; finance_sec_form_d when you need latest SEC Form D filings from EDGAR's public search index. Price: $0.002 in USDC per successful call, paid with x402 (Base, Solana or Arc); failed calls are not charged.

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

Input Schema

Name	Required	Description	Default
`crd`	No	Firm CRD number, e.g. 105958
`name`	No	Or a firm name; the first active adviser match is used

Output Schema

Name	Required	Description	Default
`crd`	No
`url`	No
`name`	No
`source`	No
`address`	No
`brochures`	No
`checkedAt`	No
`secNumber`	No
`formAdvPdf`	No
`otherNames`	No
`matchedFrom`	No
`adviserStatus`	No
`noticeFilings`	No
`registrations`	No
`secRegistered`	No
`stateRegistered`	No
`latestFormAdvFiling`	No
`exemptReportingAdviser`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses the commercial terms an agent needs before calling: $0.002 USDC per successful call via x402 on Base, Solana or Arc, with failed calls not charged. It also implies the lookup is an external network call against SEC data. It stops short of stating rate limits, latency, or what happens when neither crd nor name is supplied.

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?

Despite being longer than typical, the structure is front-loaded and purposeful: one sentence naming the resource and returned fields, one sentence routing to alternative sibling tools, one sentence stating price and payment mechanics. Each block is separable and nothing is filler, though the returned-field enumeration partially duplicates the output schema.

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 an output schema present, the tool need not explain return values, yet it still summarizes the payload shape so an agent can judge relevance before paying. Read-only and open-world behavior plus pricing are covered. Minor omissions: no guidance on which identifier to prefer when both are given, and no failure/no-match behavior.

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% and both parameters are documented there, including the 'first active adviser match' tie-breaking rule for the name parameter. The description only restates that lookup is by CRD number or firm name, adding no format, precedence, or disambiguation guidance beyond the schema, so the baseline of 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?

The description opens with a specific verb+resource+source: an investment adviser firm record from the SEC IAPD (Form ADV), keyed by CRD number or firm name. It then enumerates the returned fields (adviser status, SEC file number, registration flags, brochures) and names two sibling tools it is not, so an agent can distinguish it from finance_sec_iapd and finance_sec_form_d without opening any 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?

It explicitly routes the agent: use finance_sec_iapd for searching the IAPD and finance_sec_form_d for EDGAR Form D filings, implying this tool is the targeted single-firm lookup. The one gap is that the boundary between 'search the IAPD' and this tool's 'by firm name' lookup mode is not fully resolved, and no when-not-to-use case (e.g., broker-dealer records) is stated.

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

All SiteCheck Crypto & Finance tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?