mcp-server-il-benefits
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| IL_BENEFITS_HOME | No | Override the directory where the local wallet file is stored (defaults to ~/.config/mcp-server-il-benefits/). No API key or account is required. |
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 |
|---|---|
| best_way_to_payA | Use when the user is in or heading to a store and asks which card, club, cashback portal or discounted gift card to use. Takes a store or chain name in Hebrew or English. Makes one live request to the connected benefit sources and returns ranked options (the user's own providers first), how to use each, and a link. Always show the links and the source attribution, and tell the user to confirm at checkout. Never buys anything. |
| list_sourcesA | Show which existing benefit databases this server asks, their terms page and what they cover. Use to explain where an answer came from or why a store has no result. |
| wallet_getA | Show the cashback portals, clubs and sellers the user said they use. The wallet is a local file of names. It never leaves the machine. |
| wallet_setA | Replace the saved wallet with provider names as they appear in results (for example a cashback portal name or a gift card seller). Used to rank the user's own providers first. Store names only. Never ask for or store card numbers, balances or personal details. |
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 4 tools
Each tool has a clearly distinct purpose: best_way_to_pay queries benefits, list_sources explains data origins, wallet_get reads the saved wallet, and wallet_set writes it. The read/write pair is unambiguous, and there is no meaningful overlap between tools.
The set mixes three conventions: a natural-language phrase (best_way_to_pay), verb_noun (list_sources), and noun_verb (wallet_get, wallet_set). Names are readable but not predictable as a pattern.
Four tools map neatly onto the narrow domain (query benefits, inspect sources, read/write a wallet). It is slightly thin but each tool earns its place with no redundancy.
The surface covers query, source explanation, and wallet read/write for the benefits domain. Minor gaps exist, such as no way to add or remove individual providers (wallet_set replaces the whole list), but core workflows are served.