Skip to main content
Glama
cliwant

mcp-sam-gov

by cliwant

fdic_branch_deposits

Read-only

Retrieve FDIC branch deposit data from the annual Summary of Deposits. Filter by certificate number, state, or year to see deposit distribution across branches.

Instructions

FDIC branch-deposit footprint — the Summary of Deposits (keyless FDIC BankFind, api.fdic.gov/banks/sod): the annual June-30 branch-office deposit distribution ('where does this bank hold deposits, and how concentrated?'). Exact-key filters (all optional, AND-combined; ≥1 recommended): cert (→ CERT, the STABLE entity key), state (2-letter → STALPBR, the branch-state field, C118-quoted so Oregon is operator-safe), year (→ YEAR, the June-30 snapshot year). limit (≤1000, def 100), offset (≤100000), sortBy (allowlisted enum YEAR/DEPSUMBR, def YEAR), sortOrder (def DESC → newest snapshot / largest deposits first). Returns { branches:[{ cert, institutionName, branchNumber, branchName, city, state, zip, address, depositsUSD, year, id }] } (e.g. CERT 10004 → 74 branch-year rows). HONESTY: totalAvailable is the EXACT meta.total (stable across offset — never the page length); depositsUSD is DEPSUMBR published in $thousands, normalized to whole USD ×1000 (null-never-0 — a real 0 stays 0, absent → null); a bad/mistyped filter field can never reach the wire (server-side allowlist by construction — FDIC would otherwise return a silent total:0 false-empty, not an error); 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); the DISTINCT annual snapshot build time is disclosed. Branch facility data only (name/address/city/state/zip/deposits) — no personal/officer PII. NOTE: SOD is an annual June-30 snapshot; FDIC keys on CERT, not SAM UEI/DUNS.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
certNoFilter by FDIC certificate number (the STABLE entity key; → CERT filter). Resolve a bank's CERT via fdic_search_institutions.
yearNoFilter by Summary-of-Deposits survey YEAR (→ YEAR filter), the annual June-30 snapshot year. 1934..current UTC year.
limitNoRows per page, 1..1000, default 100.
stateNoFilter by 2-letter branch state code (uppercase; → STALPBR filter — the SOD branch-state field). e.g. 'OR'. C118-quoted so Oregon is Lucene-operator-safe.
offsetNo0-based row offset for pagination, 0..100000, default 0.
sortByNoSort field (allowlisted enum; default YEAR = snapshot year). An unknown field is rejected before fetch.
sortOrderNoSort direction, default DESC (newest snapshot / largest deposits first).
Behavior5/5

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

The description goes far beyond the readOnlyHint annotation by detailing the meaning of depositsUSD (conversion from thousands, null handling), error behavior (server-side allowlist, only honest empty is meta.total:0), and data limitations (annual snapshot, no PII). It also discusses totalAvailable behavior, adding significant context.

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 dense and informative, but somewhat long. It is front-loaded with the purpose, then lists parameters, then provides behavioral notes. Every sentence adds value, but some details could be streamlined for brevity.

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 has 7 parameters, no output schema, and no nested objects, the description is thorough: it covers all parameters, output structure, example rows, pagination, error handling, and data semantics. No important aspect is missing.

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?

Although the input schema has 100% coverage, the description adds substantial meaning: cert is the stable entity key, state uses C118 quoting, sortBy options are explained, and the returned fields (e.g., depositsUSD, institutionName) are described in context. This goes beyond the 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 states the tool retrieves FDIC branch-deposit footprints from the Summary of Deposits, specifying it provides annual June-30 branch-office deposit distribution. It uses specific verbs ('retrieve', 'footprint') and distinguishes itself from sibling tools like fdic_institution_financials by focusing on branch deposits.

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 description explains that all filters are optional and recommends using at least one, provides guidance on pagination parameters (limit, offset) and sorting, and implicitly distinguishes from other FDIC tools by the data type. However, it does not explicitly state when not to use this tool or mention alternative tools for related data.

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