Skip to main content
Glama

Banking access — opening an account, deposit protection and instant payments

banking_access
Read-onlyIdempotent

Whether a newcomer can open a personal bank account in a country (yes, restricted or no) with the documents usually asked for from a fixed vocabulary, the statutory deposit guarantee per depositor per bank in local currency AND converted to USD at the site's FX snapshot, the country's instant payment systems from the World Bank's Project FASTT tracker, the EU basic-account right under Directive 2014/92/EU where it applies, and a FATCA flag where banks commonly decline US citizens — a hand-curated register over all 186 spine countries, added 17 Sep 2026, with the scheme or regulator page and check date per row (confidence: "secondary" where the official page could not be fetched, separately on depositGuarantee for the figure). A country with no deposit-insurance scheme has NO depositGuarantee — never a zero — and a country absent from FASTT has no instantPayments, which is not the same as having no instant payments. country for one entry, countries for a side-by-side; without either, ranks by metric (depositGuaranteeUsd default, or instantPaymentsSince, whose sort=lowest lists the longest-running first), optionally narrowed by access, with countries lacking the metric in excluded. internationalOptions describes the kinds of cross-border account and what protects the money — categories only, never a named provider. For information only — not financial advice; banks set their own onboarding policies and every response says so first.

Input Schema

NameRequiredDescriptionDefault
sortNoDefaults to highest, or lowest for instantPaymentsSince (longest-running first).
limitNoMaximum rows in a ranking.
accessNoNarrow a ranking to one non-resident access rule.
metricNoRanking metric when no country is given.depositGuaranteeUsd
countryNoISO alpha-2 code for a single country, e.g. PT.
countriesNoComma-separated ISO alpha-2 codes, at least two, e.g. GB,TH,NG.

Output Schema

NameRequiredDescriptionDefault
okNo
rowsNo
caveatsNo
excludedNo
attributionNo
internationalOptionsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Goes well past the readOnly/idempotent annotations by disclosing data provenance (hand-curated over 186 spine countries, added 17 Sep 2026), per-row scheme/regulator page and check date, `confidence: "secondary"` semantics, and the critical absence-vs-zero distinction for `depositGuarantee` and `instantPayments`. It also discloses the mandatory non-advice disclaimer returned in every response.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core question is front-loaded, and every clause carries information, but it is delivered as two sprawling run-on sentences with dense parentheticals and backtick-heavy inline syntax. Readable enough, but not efficiently structured or chunked for fast agent parsing.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, the description need not explain return shape, and it still covers the interpretation traps (no scheme means no field, not zero; absent from FASTT is not the same as no instant payments) that an agent would otherwise misread. Nothing needed to call it correctly is missing.

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?

Schema coverage is 100%, so baseline is 3, but the description adds genuine meaning: `sort=lowest` flips the direction for `instantPaymentsSince` (longest-running first), `metric` defaults to `depositGuaranteeUsd`, and `access` is a narrowing filter on rankings rather than a selector for single-country lookup. This is more than restating the schema.

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+resource with unusual precision: newcomer account-opening rules, statutory deposit guarantee (local + USD), instant payment systems, EU basic-account right, and FATCA flag. An agent can distinguish this from compare_banking_access (which is a comparison sibling) without opening either schema.

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?

Explicitly routes among modes: `country` for a single entry, `countries` for a side-by-side, and neither to get a ranking by `metric` (with `sort` semantics and `access` narrowing, plus `excluded` for countries lacking the metric). It does not name the natural alternative (compare_banking_access) or state when-not-to-use, so it stops short of a 5.

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