Skip to main content
Glama

Banks reached

list_banks
Read-onlyIdempotent

Lists the banks money can be sent to in a country, with the other names people know them by. Use it when someone asks whether a particular bank is supported. Only some countries have a bank list.

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": {
      "country": "<country>"
    },
    "name": "list_banks"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryYes
currencyNo

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?

The annotations already declare this as a safe, idempotent read, so the bar is lower. The description adds useful behavioral context by saying the response includes bank aliases and that country coverage is incomplete, though it does not explain what happens when a country lacks a bank list.

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?

The description is three short sentences with no wasted wording. The core purpose is front-loaded, followed immediately by usage guidance and an important coverage caveat.

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?

For a simple read-only tool with annotations and no output schema, the description covers purpose, usage, aliases, and partial country coverage. But with 0% schema coverage, the unexplained currency parameter is a notable omission that keeps it from being fully complete.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate for both parameters. It explains that the list is scoped to a country, but it does not explain the optional currency parameter or how it affects the bank list, leaving a significant semantic gap.

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?

The description uses a specific verb and resource: it lists banks that money can be sent to in a country, and mentions that aliases are included. This clearly separates it from broader tools like get_supported_countries or get_payout_options, but it does not explicitly name or distinguish those siblings.

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?

It gives a clear use case: 'Use it when someone asks whether a particular bank is supported.' It also notes that only some countries have a bank list. However, it does not name when not to use it or point to alternatives such as get_supported_countries.

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.