mcp-expense-tracker
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| add_expenseB | Record a new expense. Date defaults to today (YYYY-MM-DD) if not provided. |
| list_expensesA | List recorded expenses, optionally filtered by date range and/or category. |
| delete_expenseA | Delete an expense by its id. |
| summarizeA | Get total spending for a day, a month, or all time, broken down by category. |
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 targets a distinct operation: add, list, summarize totals, delete. There is no overlap in purpose, making it clear which tool to use.
Three tools follow the verb_noun pattern (add_expense, list_expenses, delete_expense), but 'summarize' deviates by being a bare verb. This is a minor inconsistency.
With 4 tools, the server is well-scoped for a basic expense tracker. Each tool serves a necessary role without unnecessary bloat.
The set covers create (add_expense), read (list_expenses, summarize), and delete (delete_expense), but lacks an update operation. Agents cannot modify existing expenses, which is a notable gap.