Skip to main content
Glama

search_banks

Free. Find FDIC-insured US banks by name; returns FDIC cert numbers.

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": {
      "q": "<q>"
    },
    "name": "search_banks"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesBank name fragment

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses cost ('Free'), the read-only lookup nature, and what is returned (FDIC cert numbers, which matters since there is no output schema). It does not say whether matching is exact or partial, whether there is a result cap or pagination, or what happens on no matches.

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?

One sentence plus a cost qualifier; nothing is padded and the key facts are front-loaded. The sentence is dense but readable, with no wasted clauses.

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?

For a single-parameter lookup with no annotations or output schema, the description covers purpose, input (name-based), and output (cert numbers). Only matching behavior and result limits are absent, which are minor for a simple search tool.

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 single parameter 'q' is documented as a 'Bank name fragment', so the schema already does the work. 'By name' in the description is consistent but adds no syntax, matching rules, or formatting detail beyond the schema.

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?

States a concrete verb ('Find'), resource ('FDIC-insured US banks'), and input scope ('by name'), plus the returned identifier ('FDIC cert numbers'). That lets an agent separate it from screen_banks or get_bank_metrics, though no sibling is named explicitly.

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?

The 'Free' prefix and 'by name' framing imply this is the cheap name-based lookup step and that metric-based selection belongs elsewhere, but the description never states when to prefer it over the sibling tools or what it should be used before/after. Usage 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