Skip to main content
Glama

Bank us

bank_us
Read-onlyIdempotent

Use when an agent needs to identify or vet a US bank: by name or FDIC cert returns FDIC data: active or closed, charter class, regulator, city/state, website, total assets and report date. Returns the paid x402 request for your input (GET /bank/us, $0.005 per call; schema linked). Call that URL with an x402 or MPP client to get the data. Bad input is refused before any charge. First call each day returns the data itself, free; later calls return the paid request.

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": "bank_us"
  }
}

Input Schema

NameRequiredDescriptionDefault
certNoFDIC certificate number (1-6 digits). Use name or cert
nameNoBank name (phrase match; the largest active match is returned, others listed). Use name or cert

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing the payment model (x402, $0.005 per call), the exact endpoint, the fact that bad input is refused before any charge, and the unusual dual-mode behavior where the first call each day returns data free and later calls return the paid request. These are non-obvious operational traits an agent must know before calling.

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?

Front-loaded with the usage trigger, and every sentence carries operational information (fields, cost, endpoint, error handling, free-first-call rule). The first sentence is a long run-on that could be split for readability, but there is no filler.

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 compensates by enumerating the returned fields, and it fully explains the payment/retrieval flow. The one soft spot is that the interplay between 'returns the paid request' and 'first call returns the data itself' could be spelled out more concretely, but an agent has enough to act.

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 coverage is 100% and the schema itself already documents the cert pattern and the name phrase-match/largest-match behavior. The description only restates 'by name or FDIC cert' without adding format or disambiguation rules, 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?

States a specific verb and resource ('identify or vet a US bank'), the two lookup keys (name or FDIC cert), and enumerates the returned fields (active/closed, charter class, regulator, city/state, website, total assets, report date). This is clearly distinguishable from sibling tools like sanctions_screening or wallet_risk.

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?

Opens with an explicit trigger ('Use when an agent needs to identify or vet a US bank') and names both input modes. It does not, however, state when NOT to use it or point to a related sibling for complementary checks (e.g., sanctions screening of a bank).

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