ameria-bank
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AMERIA_TOKEN | No | Refresh token from MyAmeria. Not required if using a vault. | |
| AMERIA_VAULT | No | Vault backend: 1password or keychain | |
| AMERIA_CLIENT_ID | No | Client-Id header value for API calls. Not required if using a vault. | |
| AMERIA_VAULT_KEY | No | Item name in the vault (e.g. ameria-mcp) | |
| AMERIA_CLIENT_AUTH | No | Base64-encoded client_id:client_secret for the token endpoint. Not required if using a vault. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_transactionsA | Get transaction history from Ameria Bank. Returns a page of transactions within a date range. Defaults to last 30 days. Use page parameter to paginate — check hasNext in the response to know if more pages exist. For finding specific merchants, prefer search_transactions instead. |
| search_transactionsA | Search Ameria Bank transactions by keyword within a date range. Filters against merchant names, transfer descriptions, and beneficiary names (case-insensitive). IMPORTANT: searches within a single page only — to find all matches, iterate through pages or use a larger page size. Useful for questions like 'how much did I spend on YANDEX this month?'. |
| get_accounts_and_cardsA | Get all accounts and cards from Ameria Bank. Returns balances, card types, statuses, overdraft info, and product IDs. Includes both Ameria cards and linked external cards. Call this FIRST to discover available account/card IDs before using get_available_balance or get_account_events. |
| get_available_balanceA | Get detailed balance breakdown for a specific card or account. Returns balance, available balance, frozen balance, and offline available amount. Use get_accounts_and_cards first to find the product ID. |
| get_account_eventsA | Get past events (transactions) for a specific Ameria Bank account. Filters by account and minimum amount. Use get_accounts_and_cards first to find the accountId — use the 'accountId' field from cards or 'id' field from accounts (e.g. '31023550200'). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
get_transactions and get_account_events both retrieve transactions—one broadly, one per account—creating overlap. search_transactions provides keyword filtering but its single-page limitation blurs its boundaries with get_transactions. get_available_balance is distinct, but the transaction trio causes moderate ambiguity.
Most tool names follow a consistent verb_noun pattern (get_transactions, search_transactions, get_accounts_and_cards, get_available_balance, get_account_events). However, 'get_accounts_and_cards' deviates by returning two resource types, slightly breaking the pattern.
With only 5 tools, the set is well-scoped for a bank integration, covering browsing accounts, checking balances, and retrieving/searching transactions without bloat.
The surface covers read operations for accounts and transactions but lacks any write capabilities (e.g., transfers, payments) and missing account details like statements or card management. This is a notable gap for a banking domain.