expense-tracker-mcp-server
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
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| add_expenseC | Add a new expense entry to the database. |
| list_expensesA | List expense entries within an inclusive date range. |
| summarizeA | Summarize expenses by category within an inclusive date range. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| categories |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: add_expense writes entries, list_expenses reads them by date range, and summarize aggregates them by category. There is no ambiguity between the three tools.
All tools use a consistent verb_infinitive arrangement (add_, list_, summarize), though adding and listing are verb_noun patterns while summarize is less obviously named in the same convention. Minor deviation but the pattern is predictable.
Three tools is on the thin side for an expense tracker, which typically needs update and delete operations to manage entries. The count is minimal but each tool does carry meaningful weight.
The surface covers create (add) and read (list, summarize), but lacks update and delete operations for expenses—a clear gap in CRUD coverage. Users cannot edit or remove entries, which is a significant functionality hole for an expense tracker.