Skip to main content
Glama
cliwant

mcp-sam-gov

by cliwant

fdic_risk_ratios

Read-only

Retrieve FDIC financial risk ratios, including profitability, capital adequacy, and asset quality, for an institution by its certificate number.

Instructions

FDIC counterparty RISK RATIOS for ONE institution by certificate number (keyless FDIC BankFind, api.fdic.gov/banks/financials) — the SOUNDNESS lane the balance-sheet tools cannot express: profitability (ROA/pretax ROA/ROE), net interest margin, efficiency ratio, asset quality (net charge-offs to loans), capital adequacy (leverage, tier-1 risk-based, total risk-based ratios) + the tier-1 capital LEVEL. Input cert (REQUIRED FDIC certificate number, from fdic_search_institutions), reportDate (optional YYYYMMDD quarter-end → REPDTE; omit for the full quarterly time-series), limit (≤1000, def 100), offset (≤100000), sortBy (allowlisted enum REPDTE/ROA/ROE/RBCRWAJ/EEFFR, def REPDTE), sortOrder (def DESC → newest quarter first). Returns { cert, ratios:[{ cert, reportDate, cblrFramework, returnOnAssetsPct, preTaxReturnOnAssetsPct, returnOnEquityPct, netInterestMarginPct, efficiencyRatioPct, netChargeOffsToLoansPct, leverageRatioPct, tier1RiskBasedCapitalRatioPct, totalRiskBasedCapitalRatioPct, tier1CapitalUSD, id }] }. ★UNITS-IN-THE-KEY: every *Pct field is an FDIC-published PERCENTAGE surfaced VERBATIM (no scaling, no recompute) — do NOT read it as a dollar amount or ×1000-scale it; tier1CapitalUSD is a DOLLAR amount (FDIC publishes it in $thousands, normalized ×1000). ★NULL-NEVER-0: a not-reported ratio is null (never 0% — a false 'no return / no capital'). ★CBLR (community-bank-leverage) banks (cblrFramework:true) do NOT report the risk-based capital ratios — FDIC returns a literal 0 for the total risk-based ratio, which this tool maps to null for BOTH tier1RiskBasedCapitalRatioPct and totalRiskBasedCapitalRatioPct (a null there is a normal framework artifact, read alongside leverageRatioPct — NOT a 0% capital red flag). No ratio is recomputed; each is exactly FDIC's published Call-Report figure. HONESTY: totalAvailable is the EXACT meta.total (stable across offset); 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 snapshot build time is disclosed. NOTE: reported regulatory metrics, NOT a soundness rating or failure prediction; FDIC keys on CERT, not SAM UEI/DUNS.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
certYesREQUIRED FDIC certificate number of the institution (→ CERT filter). From fdic_search_institutions.
limitNoRows per page, 1..1000, default 100.
offsetNo0-based row offset for pagination, 0..100000, default 0.
sortByNoSort field (allowlisted enum; default REPDTE = report date). An unknown field is rejected before fetch.
sortOrderNoSort direction, default DESC (newest quarter first).
reportDateNoOptional report date (→ REPDTE filter), a quarter-end as a YYYYMMDD integer (e.g. 20240630). Omit for the full quarterly ratio time-series.
Behavior5/5

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

Annotations already declare readOnlyHint and openWorldHint. Description extends with units (percent vs dollars, scaling), null handling (null vs 0, CBLR mapping), response structure, error behavior (throws on non-standard responses), and disclosure of no recomputation. No contradiction with annotations.

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 length, every sentence earns its place. Structured logically: purpose, parameters, units, nulls, CBLR, honesty, disclaimer. Front-loaded with main purpose. No redundant information.

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?

For a tool with 6 parameters, no output schema, but high schema coverage, the description is exceptionally complete. It explains response structure (ratios array with fields), error handling, units, null behavior, and relationship to sibling tools. No 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 significant value: explains cert's relation to fdic_search_institutions, reportDate format and effect, sortBy enum meaning and default, sortOrder default, limit/offset constraints. Every parameter is enriched beyond 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 it retrieves FDIC counterparty risk ratios for one institution by certificate number, using specific verbs (get, express) and resource (risk ratios). It distinguishes itself from sibling balance-sheet tools by calling itself the 'soundness lane' they cannot express.

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

Usage Guidelines5/5

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

Explicitly says to use this tool for risk ratios and contrasts with balance-sheet tools. Provides prerequisite: input cert from fdic_search_institutions. Also notes it is not a soundness rating or failure prediction, guiding appropriate use.

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