Expense Tracker 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": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| add_expenseA | Add a new expense. category and subcategory are required and must come from the data://categories resource. If a category's subcategory list is empty, any descriptive subcategory text is acceptable, but it must not be left blank. |
| list_expensesA | List expenses, optionally filtered by category and/or date range (YYYY-MM-DD). |
| update_expenseA | Update an existing expense. Only provided fields are changed. category and subcategory must come from the data://categories resource. |
| delete_expenseB | Delete an expense by id. |
| add_creditC | Add credit (money received) to the tracker. |
| list_creditsB | List credits, optionally filtered by date range (YYYY-MM-DD). |
| summarize_expensesB | Summarize expenses by category, optionally filtered by date range (YYYY-MM-DD). |
| get_balanceA | Get total credited, total spent, and remaining balance. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| get_categories | Map of allowed expense categories to their allowed subcategories. Always pick category and subcategory from here when adding or updating an expense. An empty subcategory list means any subcategory text is acceptable for that category. |
TDQS
Scored across 8 tools
Each tool targets a distinct resource and action: expenses have add/list/update/delete, credits have add/list, and summarize/get_balance provide reporting. There is no meaningful overlap or ambiguity between tools.
All tools follow a clear verb_noun snake_case pattern. List operations use plural nouns (list_expenses, list_credits) while singular entity operations use singular nouns, which is a predictable and consistent convention.
Eight tools is well-scoped for an expense tracker: full CRUD for expenses, credit tracking, and balance/summary reporting. Each tool earns its place without redundancy or bloat.
Expenses have complete CRUD coverage and reporting is solid, but credits only support add and list with no update or delete. This is a minor gap that agents can work around by re-adding corrected credits, but it is a slight lifecycle gap.