Skip to main content
Glama

Bank Search Index

bank_search_index
Read-onlyIdempotent

Full lightweight bank universe list for client-side typeahead. Requires a free account/API key. (Source: FFIEC + FDIC.) Dollar amounts are in thousands of US dollars ($000s); ratios are percentages.

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_search_index"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world), so the description clears a lower bar and adds genuinely useful context: a free account/API key is required, and the upstream sources are FFIEC + FDIC. The trailing units sentence ($000s, percentages) looks like boilerplate for a zero-parameter index listing rather than a property of this call, which slightly muddies rather than clarifies.

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?

Three short sentences, with the core purpose front-loaded before the auth requirement and provenance. The final units sentence does not earn its place for a zero-arg list tool, which is the one clear piece of waste.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 carries the burden of describing what comes back, and "lightweight" is the only hint about which fields the typeahead index contains or how large it is. Auth requirements and sources are covered, but an agent still cannot tell whether the payload is names+IDs only or includes assets and ratios, nor whether it is paginated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes no parameters, so the 4 baseline applies and there is no parameter meaning to convey or omit. The added unit conventions do not map to any input and thus add nothing here, but they do not detract from parameter understanding.

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?

"Full lightweight bank universe list for client-side typeahead" names a specific resource (bank universe list) with a stated form factor (lightweight) and an intended consumer (typeahead). It implicitly contrasts with the filtered lookup siblings (banks, bank_search_*), but never names an alternative, so differentiation is left to inference.

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?

"for client-side typeahead" is the only usage signal, and it does imply when this beats a filtered search endpoint. There is no explicit when-not guidance, no mention of cost/size tradeoff versus calling a targeted bank lookup, and no guidance on caching the result client-side.

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