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. |
| 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 3 tools
The three tools have clearly distinct purposes: add_expense creates a record, list_expenses retrieves raw records, and summarize aggregates by category. There is no overlap or ambiguity between them.
All tools use lowercase snake_case and a verb-first pattern (add_, list_, summarize). The only minor inconsistency is that 'summarize' omits the explicit noun 'expenses' that the other two include, but it remains predictable and readable.
Three tools is a reasonable size for a focused expense tracker. It is slightly minimal but each tool serves a distinct core function (insert, query, aggregate), so the count feels appropriate rather than inadequate.
The surface covers basic recording, viewing, and summarizing expenses, but lacks update and delete operations, which are common expected capabilities in a data management domain. This is a notable gap that agents cannot easily work around.