Israeli Bank MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| fetch-transactionsD | – |
| two-factor-authD | – |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| banks |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: 'fetch-transactions' retrieves transaction data, while 'two-factor-auth' handles authentication. There is no overlap or ambiguity between these functions, making it easy for an agent to select the correct tool.
Both tools use a consistent verb-noun pattern with hyphens (e.g., 'fetch-transactions', 'two-factor-auth'), which is predictable and readable. The minor deviation is that 'two-factor-auth' uses a compound noun without a clear verb, but overall the naming is coherent.
With only two tools, the server feels thin for a banking domain, which typically requires operations like account management, transfers, balances, or payments. This limited set may not cover essential banking workflows, indicating an under-scoped tool surface.
The tool set is severely incomplete for a banking server. It lacks basic operations such as checking account balances, initiating transfers, managing accounts, or handling payments. The two tools provided do not form a functional banking interface, leading to significant gaps that will cause agent failures.