Skip to main content
Glama

FDIC Bank Demographics

fdic_demographics
Read-onlyIdempotent

FDIC institution demographics for one bank - CBSA/metro-micro classification, minority-status designation, head-office latitude/longitude, web URL, and office-count rollups, by as-of quarter. (Source: FDIC Institution Directory.)

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": {
      "rssd_id": "<rssd_id>"
    },
    "name": "fdic_demographics"
  }
}

Input Schema

NameRequiredDescriptionDefault
rssd_idYesFederal Reserve RSSD id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds the data source (FDIC Institution Directory) and the as-of-quarter semantics, which is useful context, but says nothing about what happens for an unknown rssd_id, data vintage, or missing fields.

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?

A single front-loaded sentence with the resource and scope stated first, then the field inventory, then the source citation. It is dense but every clause conveys information; only the parenthetical source attribution is marginal.

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?

With no output schema, the description usefully enumerates the returned fields so an agent knows what it will get, and the read-only nature is handled by annotations. Gaps are minor: no note on missing/partial data or response shape, but an agent can call it correctly from this.

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?

Only one parameter, and the schema documents rssd_id at 100% coverage ('Federal Reserve RSSD id.' with an example). The description adds little meaning beyond confirming the tool operates on exactly one bank, so the baseline of 3 applies when the schema carries the load.

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?

Names a specific resource (FDIC institution demographics) scoped to a single bank and enumerates the returned fields: CBSA/metro-micro classification, minority status, head-office lat/long, web URL, and office-count rollups. This is well beyond a tautology, though it does not explicitly contrast itself with siblings like fdic_financials or bank_profile.

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?

'for one bank' and 'by as-of quarter' imply a single-institution lookup rather than a rollup, but there is no explicit statement of when to use this versus fdic_financials, bank_profile, or the branch tools, and no exclusions or prerequisites. Guidance is only inferable.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources