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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| add_expenseC | Add a new expense entry to the database. |
| list_expensesC | List expense entries within an inclusive date range. |
| delete_expenseC | Delete an expense entry by its ID. |
| update_expenseC | Update an existing expense entry. |
| summarizeB | 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 5 tools
Each tool has a clearly distinct purpose: add, delete, list, summarize, and update. No overlap or ambiguity.
Four tools follow verb_noun pattern (add_expense, delete_expense, list_expenses, update_expense), but 'summarize' lacks a noun, which is a minor inconsistency.
Five tools is well-scoped for an expense tracker, covering essential operations without being excessive or insufficient.
CRUD operations are present (add, delete, update) along with listing and summarization. Missing a get_expense by ID, but list by date range covers retrieval adequately. Minor gap in filtering without summary.