Skip to main content
Glama
cliwant

mcp-sam-gov

by cliwant

fdic_search_institutions

Read-only

Search FDIC-insured institutions for bank due diligence using filters like name, state, city, or certificate number. Paginate and sort results.

Instructions

Search the FDIC-insured-institution directory (keyless FDIC BankFind, api.fdic.gov/banks/institutions) — a regulated-entity directory for B2G counterparty / bank due-diligence. Structured filters: state (2-letter, → STALP), activeOnly (→ ACTIVE 1/0), cert (→ CERT, the STABLE entity key), plus name/city matched via FDIC's case-insensitive full-text search param (NOT filtersfilters=NAME:"chase" is case-sensitive exact-keyword and returns a false-empty; search=NAME:chase finds JPMorgan Chase etc.). limit (≤1000, def 100), offset (≤100000), sortBy (allowlisted enum NAME/CERT/ASSET/ESTYMD/STALP/CITY/ACTIVE), sortOrder (ASC/DESC). Returns { institutions:[{ name, city, state, cert, assetUSD, active, establishedDate, id }] }. HONESTY: totalAvailable is the EXACT meta.total (stable across offset — never the page length); ASSET is published in $thousands and normalized to whole USD ×1000 (null-never-0 — a real 0 stays 0, absent → null); the ONLY honest empty is meta.total:0/data:[] ⇒ complete:true/total:0, every other envelope (400 errors[]/404/non-JSON/missing meta or data) THROWS (never a fake empty); a multi-word name/city is matched per-token (disclosed); the point-in-time snapshot build time is disclosed. NOTE: FDIC keys on CERT, not SAM UEI/DUNS.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
certNoFilter by FDIC certificate number (the STABLE entity key; → CERT filter).
cityNoFilter by CITY via FDIC full-text `search` (case-insensitive token match).
nameNoFilter by institution NAME via FDIC full-text `search` (case-insensitive token match; NOT case-sensitive exact-keyword — that is why we route to `search`, not `filters`).
limitNoRows per page, 1..1000, default 100.
stateNoFilter by 2-letter US state code (uppercase; → STALP filter). e.g. 'VA'.
offsetNo0-based row offset for pagination, 0..100000, default 0.
sortByNoOptional sort field (an allowlisted enum; an unknown field is rejected before fetch).
sortOrderNoSort direction when sortBy is set, ASC (default) or DESC.
activeOnlyNoFilter to active (true → ACTIVE:1) or inactive (false → ACTIVE:0) institutions; omit for both.
Behavior5/5

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

Extensive disclosure beyond annotations: explains exact behavior of totalAvailable, ASSET normalization (null vs 0), error handling (throws, not fake empties), multi-word token matching, and point-in-time snapshot. No contradiction with readOnlyHint/openWorldHint.

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

Conciseness3/5

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

Description is informative but lengthy and dense, with a single-paragraph structure that may overwhelm. The 'HONESTY' section adds value but reduces conciseness. Could be more structured with bullet points.

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 9 parameters, no output schema, and only readOnlyHint/openWorldHint annotations, the description is remarkably complete: covers return format, pagination, null handling, error behavior, and even the underlying API's key scheme (CERT). Leaves no major gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but description adds critical nuance: distinguishes case-sensitive 'filters' from full-text 'search' for name/city, explains sortBy is allowlisted and rejected before fetch, and specifies default/limits for limit/offset. Adds significant value beyond schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool searches the FDIC-insured institution directory for due diligence, using specific verb and resource. It does not explicitly differentiate from sibling FDIC tools like financials or failures, but the context implies a directory search.

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?

Provides detailed how-to (case-sensitive vs full-text, pagination) but does not explicitly specify when to use this vs alternatives. Implicitly positioned for bank due-diligence but lacks direct comparison to siblings.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/cliwant/mcp-sam-gov'

If you have feedback or need assistance with the MCP directory API, please join our Discord server