Skip to main content
Glama

list_banking_accounts

Read-onlyIdempotent

List banking accounts

Lists the account's banking rails and their details — for an on-ramp, the routing and account numbers to give whoever is paying in. The off-ramp deposit address is deliberately withheld: it is internal payout plumbing, not account detail.

Free.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
accountsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties
      Added value: +{
      +  "accounts": {
      +    "items": {
      +      "description": "One banking rail on the account. An on-ramp carries the virtual bank details to give whoever is paying in. An off-ramp carries the destination it pays out to; its own funding address is internal payout plumbing and is never returned. Responses can carry further internal fields, so read the ones you need and tolerate the rest.",
      +      "properties": {
      +        "accountId": {
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        },
      +        "accountType": {
      +          "description": "One of: onramp, offramp.",
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        },
      +        "bankAccount": {
      +          "description": "On-ramp only: the virtual bank account dollars are sent to. These are the details to give whoever is paying the account. The field names inside are our banking partner's own, which is why they are snake_case where the rest of this object is camelCase.",
      +          "properties": {
      +            "aba_routing_number": {
      +              "type": [
      +                "string",
      +                "null"
      +              ]
      +            },
      +            "aba_wire_routing_number": {
      +              "type": [
      +                "string",
      +                "null"
      +              ]
      +            },
      +            "account_holder_name": {
      +              "type": [
      +                "string",
      +                "null"
      +              ]
      +            },
      +            "account_number": {
      +              "type": [
      +                "string",
      +                "null"
      +              ]
      +            },
      +            "account_type": {
      +              "type": [
      +                "string",
      +                "null"
      +              ]
      +            },
      +            "bank_address": {
      +              "type": [
      +                "object",
      +                "null"
      +              ]
      +            },
      +            "bank_name": {
      +              "type": [
      +                "string",
      +                "null"
      +              ]
      +            },
      +            "bic": {
      +              "type": [
      +                "string",
      +                "null"
      +              ]
      +            },
      +            "iban": {
      +              "type": [
      +                "string",
      +                "null"
      +              ]
      +            }
      +          },
      +          "type": [
      +            "object",
      +            "null"
      +          ]
      +        },
      +        "closedTimestamp": {
      +          "description": "Present once `status` is `closed`. Milliseconds since the epoch.",
      +          "type": [
      +            "number",
      +            "null"
      +          ]
      +        },
      +        "closedTimestampReadable": {
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        },
      +        "createdTimestamp": {
      +          "description": "Milliseconds since the epoch.",
      +          "type": [
      +            "number",
      +            "null"
      +          ]
      +        },
      +        "createdTimestampReadable": {
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        },
      +        "destinationAsset": {
      +          "description": "What comes out: the crypto asset on an on-ramp, the fiat currency on an off-ramp.",
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        },
      +        "fiatDestinationId": {
      +          "description": "Off-ramp only: the id of the destination payouts go to. `payoutDestination` is the readable form of the same thing.",
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        },
      +        "nickname": {
      +          "description": "The account owner's name for the off-ramp's payout destination, when they have set one. Lead with it when you name the account, because it is the label they chose. On-ramps have no destination and so never carry one.",
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        },
      +        "payoutDestination": {
      +          "description": "The bank account an off-ramp pays out to, summarized so a caller can confirm where the money lands without a second lookup. The account number is masked to its last four digits, which is enough to recognize the account and not enough to reuse it.",
      +          "properties": {
      +            "accountHolderName": {
      +              "type": [
      +                "string",
      +                "null"
      +              ]
      +            },
      +            "accountNumberLast4": {
      +              "description": "The last four digits of the account number. The full number is never returned here.",
      +              "type": [
      +                "string",
      +                "null"
      +              ]
      +            },
      +            "accountType": {
      +              "description": "One of: checking, savings.",
      +              "type": [
      +                "string",
      +                "null"
      +              ]
      +            },
      +            "bankName": {
      +              "type": [
      +                "string",
      +                "null"
      +              ]
      +            },
      +            "capabilities": {
      +              "description": "The rails this destination supports.",
      +              "items": {
      +                "type": [
      +                  "string",
      +                  "null"
      +                ]
      +              },
      +              "type": [
      +                "array",
      +                "null"
      +              ]
      +            },
      +            "destinationId": {
      +              "description": "The destination id, the same value `addBankingDestination` returned.",
      +              "type": [
      +                "string",
      +                "null"
      +              ]
      +            },
      +            "destinationType": {
      +              "description": "One of: fiat_us, fiat_iban, crypto.",
      +              "type": [
      +                "string",
      +                "null"
      +              ]
      +            },
      +            "name": {
      +              "description": "The label given when the destination was created.",
      +              "type": [
      +                "string",
      +                "null"
      +              ]
      +            },
      +            "routingNumber": {
      +              "description": "The full routing number. It identifies the bank rather than the account, so it is not masked.",
      +              "type": [
      +                "string",
      +                "null"
      +              ]
      +            }
      +          },
      +          "type": [
      +            "object",
      +            "null"
      +          ]
      +        },
      +        "rail": {
      +          "description": "The payment rail the account settles on.",
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        },
      +        "sourceAsset": {
      +          "description": "What goes in: the fiat currency on an on-ramp, the crypto asset on an off-ramp.",
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        },
      +        "sourceNetworkId": {
      +          "description": "Off-ramp only: the chain the funding leg arrives on.",
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        },
      +        "status": {
      +          "description": "`active` once the rail is provisioned, `closed` once our banking partner has retired it. A closed account keeps appearing here for the record and cannot be used again. Calling `createBankingAccount` provisions a fresh one rather than reviving it. One of: active, closed.",
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        }
      +      },
      +      "type": [
      +        "object",
      +        "null"
      +      ]
      +    },
      +    "type": [
      +      "array",
      +      "null"
      +    ]
      +  }
      +}
  2. Changed2 schema fields changed
    • removedInput schema / properties / auth_token
      Removed value: -{
      -  "description": "Laso credential. Only if the MCP connection has no Authorization header.",
      -  "type": "string"
      -}
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "type": "object"
      +}
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
      -  "type": "object"
      -}New value: +null
  4. First observed

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already declare a safe, idempotent, non-destructive read, so the description is not carrying the safety burden. It still adds real behavioral context the annotations cannot: the off-ramp deposit address is deliberately omitted as internal payout plumbing, so the agent knows the result is intentionally partial, and 'Free' signals no cost.

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 purpose, then a compact explanation of rail contents and the deliberate omission. The trailing 'Free.' is a terse, slightly clipped fragment but it does convey a distinct fact, so nothing is wasted.

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?

An output schema exists, so return values need not be spelled out, and with no inputs there is nothing else to document. The description covers the one thing an agent could misread, namely why off-ramp details are absent, leaving only the sibling-differentiation gap.

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 zero parameters, so there is no parameter semantics to explain and the baseline of 4 applies. The description makes no attempt to invent parameter detail, which is correct here.

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 specific verb and resource ('List banking accounts') and goes further to explain what those accounts are: banking rails with routing and account numbers for on-ramp payers. It is clear enough to distinguish from write siblings like create_banking_account, but it does not explicitly contrast with read siblings such as get_banking_profile_status.

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 rather than stated: the on-ramp/routing-number framing tells the agent this is the tool to call when a payer needs deposit details. There is no explicit 'use this when' clause, no exclusions, and no named alternative for off-ramp payout details, so the agent must infer the boundary.

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