budget-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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| pingA | Placeholder tool to verify the server is wired up correctly. |
| add_transactionA | Insert a transaction and return it plus the category's running total for its month. date: ISO 8601 'YYYY-MM-DD'. amount: dollars, signed (negative = expense, positive = income), precise to the cent. category: must already exist in the budgets table. |
| get_spending_summaryA | Summarize expense transactions (amount < 0) over a period, grouped by category or source. period: 'this_month', 'last_month', or 'custom' (requires start_date and end_date). group_by: 'category' or 'source'. start_date/end_date: ISO 8601 'YYYY-MM-DD', inclusive, only used when period='custom'. |
| categorize_transactionA | Suggest a budget category for a raw transaction description via an LLM classifier. description: raw text as it might appear on a statement, e.g. "TESCO STORES 3421 LONDON". Returns category (one of rent/food/transport/savings/business_expense/ entertainment/other), confidence (0-1), and reasoning. The category is checked against the allowed list before being returned - an invalid category from the model surfaces as an error rather than being passed through. |
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: ping for connectivity, add_transaction for inserting data, get_spending_summary for aggregating, and categorize_transaction for classification. There is no functional overlap between any two tools.
The three functional tools follow a consistent verb_noun pattern (add_transaction, get_spending_summary, categorize_transaction). The 'ping' tool breaks the pattern by being a bare verb, but it's a standard placeholder and doesn't cause confusion.
With only 4 tools (one being a placeholder), the server feels under-scoped for a budget application. The count is borderline acceptable, but the lack of essential operations makes it seem thin.
The server lacks core CRUD functionality: no way to list, update, or delete transactions, and no way to manage categories (add_transaction requires an existing category but there's no create_category tool). Also missing budget-setting features, making the surface significantly incomplete.