FDIC BankFind

get_county_branches

Get all bank branches in a county ranked by deposits.

Returns branch-level deposit data from the Summary of Deposits (SOD)
for all institutions in the specified county.

Args:
    state_fips: Two-digit state FIPS code (e.g. '06' for California).
    county_fips: Three-digit county FIPS code (e.g. '037' for Los Angeles).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "state_fips": "<state_fips>",
      "county_fips": "<county_fips>"
    },
    "name": "get_county_branches"
  }
}

Input Schema

Name	Required	Description	Default
`state_fips`	Yes
`county_fips`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedApr 7, 2026

TDQS

A3.9/5.0

Behavior3/5

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

No annotations exist, so description carries full burden. It mentions the output is ranked by deposits and sourced from SOD, but does not disclose data freshness, pagination, or completeness. Provides adequate transparency for a read operation.

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?

Concise two-paragraph description with clear function and args section. No unnecessary words, front-loads main purpose.

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?

Provides essential info for a simple lookup tool. Output schema exists but return details are not in description; mentions ranking but not order. Still fairly complete given tool complexity.

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?

With 0% schema description coverage, the description fully explains both parameters: state_fips and county_fips, including FIPS format and examples. This adds significant value beyond the schema.

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 gets all bank branches in a county ranked by deposits, specifying the data source (Summary of Deposits). This distinguishes it from siblings like get_institution_branches (likely for a specific institution) and search_institutions.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives like get_institution_branches or search_institutions. The description only provides input parameters without usage context or exclusions.

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

All FDIC BankFind 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?