Skip to main content
Glama

BRAINIAC Company Registries & Supervision

Look up FDIC BankFind institutions

registry-intelligence_fdic-bankfind-lookup
Read-onlyIdempotent

Search the vendored FDIC institutions snapshot by name, certificate number, city, or state. Returns candidate matches from the snapshot only. Price $0.03 USDC. POST /api/v1/registry-intelligence/fdic-bankfind-lookup. An unpaid call returns the x402 payment terms and does not run.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "registry-intelligence_fdic-bankfind-lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
certNocert, string, length 1 to 16. Optional.
cityNocity, string, length 1 to 100. Optional.
nameNoname, string, length 1 to 200. Optional.
limitNolimit, integer, from 1 to 25. Required.
stateNostate, string, length 2 to 32. Optional.

Output Schema

NameRequiredDescriptionDefault
matchesNomatches. Array.
sourcesNosources. Array.
limitationsNolimitations. Array.
retrievedAtNoretrievedAt. String.
totalIndexedNototalIndexed. Number.
snapshotAvailableNosnapshotAvailable. Boolean.
snapshotRetrievedAtNosnapshotRetrievedAt. String.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Annotations already declare it read-only, idempotent, non-destructive, and open-world, but the description adds non-obvious operational facts annotations cannot carry: a $0.03 USDC price, the concrete endpoint, and that an unpaid call short-circuits to payment terms rather than running the lookup. That payment-gating behavior is exactly the kind of preconditions an agent needs before invoking a metered tool.

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?

Four short sentences with the purpose front-loaded, followed by the snapshot-only constraint, price, endpoint, and payment behavior. No redundant or filler language; every sentence carries distinct information.

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 an output schema present, return-value explanation is unnecessary, and the description covers purpose, scope limits, cost, and payment failure mode adequately for a simple lookup tool. Minor gaps remain, such as no mention of how multiple filters interact or default result-size behavior, but nothing critical to a correct call is missing.

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?

Schema description coverage is 100%, so the schema already documents types, lengths, and bounds for cert, city, name, state, and limit. The description echoes the same filter names without adding semantics such as matching behavior (exact vs partial), whether filters combine with AND, or what limit controls, so baseline 3 applies.

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 gives a specific verb ("Search") plus the exact resource ("vendored FDIC institutions snapshot") and names the four filter axes: name, certificate number, city, state. It also constrains the result set ("candidate matches from the snapshot only"), so an agent knows precisely what this tool will and will not return.

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?

Usage is implied by the search-by-field framing, and the description usefully states that an unpaid call returns x402 payment terms instead of executing, which prevents a wasted invocation. However, there is no explicit when-to-use/when-not guidance or routing to alternatives, so the agent must infer that this is the tool for FDIC-institution lookups.

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