FDIC BankFind MCP Server

Analyze Securities Portfolio

fdic_analyze_securities_portfolio

Read-onlyIdempotent

Assess securities portfolio size, composition, and concentration risk for FDIC-insured institutions. Identifies MBS concentration and interest-rate exposure, returning structured JSON.

Instructions

Analyze securities portfolio size, composition, and concentration risk for an FDIC-insured institution.

Output includes:

Securities relative to total assets and capital
MBS concentration within the securities portfolio
AFS/HTM breakdown (when available)
Risk signals for portfolio concentration and interest rate exposure
Structured JSON for programmatic consumption

NOTE: This is an analytical tool based on public financial data. AFS/HTM breakdown is not currently available from the FDIC API.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`cert`	Yes	FDIC Certificate Number
`repdte`	No	Report date (YYYYMMDD). Defaults to most recent quarter.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv3.0.1Sep 22, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedInput schema / properties / cert / maximum
```
Added value: +9007199254740991
```

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

changedOutput schema / additionalProperties
```
Previous value: -trueNew value: +{}
```

Addedv1.26.0May 1, 2026

TDQS

A3.9/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. The description adds context by stating it is based on public financial data and explicitly noting that AFS/HTM breakdown is not currently available from the FDIC API. This limitation is useful beyond what annotations convey, enhancing transparency.

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 well-structured with a clear lead sentence, a concise bullet list of outputs, and a NOTE for the limitation. It is front-loaded with purpose and avoids fluff. The bullet list is slightly lengthy but each item adds value.

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?

Given the presence of an output schema (as indicated by context), the description need not detail return values. It covers the tool's purpose, scope, and a key limitation. It does not mention error cases or prerequisites, but for a read-only analytical tool with clear annotations, this is sufficient.

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?

Input schema has 100% coverage—both parameters (cert and repdte) have descriptions. The description does not add any parameter-specific meaning beyond what the schema provides, such as format details or dependencies. Baseline 3 is appropriate since the schema carries the full burden.

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 states the tool analyzes securities portfolio size, composition, and concentration risk for FDIC-insured institutions. It enumerates specific outputs (relative to assets/capital, MBS concentration, AFS/HTM breakdown, risk signals), distinguishing it from sibling analysis tools like credit concentration or funding profile.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage through its specific focus on securities portfolios, but it does not explicitly mention when to use this tool versus alternatives. There is no statement of 'use when...' or 'not for...' or mention of sibling tools. The NOTE about AFS/HTM unavailability provides a minor limitation, but no routing guidance.

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