BudgetBakers Wallet MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WALLET_API_TOKEN | Yes | Your Wallet API Token |
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 |
|---|---|
| list_accountsD | – |
| list_recordsD | – |
| list_categoriesD | – |
| list_labelsD | – |
| get_api_usageD | – |
| create_recordsD | – |
| update_recordsD | – |
| delete_recordsD | – |
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 8 tools
Each tool targets a distinct resource or action: accounts, records, categories, labels, API usage, and CRUD operations on records. The names clearly separate listing from mutation, and get_api_usage is unique.
All tool names follow a consistent lower_snake_case verb_noun pattern: list_* for retrieval, create_/update_/delete_records for mutations, and get_api_usage. No mixed conventions or vague verbs.
8 tools is well-scoped for a wallet management server, covering core resources and CRUD for records without excessive bloat. Each tool has a clear purpose.
Records have full CRUD (create, update, delete, list), and accounts/categories/labels have list operations. However, missing single-item getters and CRUD for non-record resources create minor gaps that agents can work around via listing.