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
} |
| 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: adding, listing, and summarizing expenses. There is no overlap or ambiguity in functionality.
The first two tools follow a verb_noun pattern (add_expense, list_expenses), but the third tool is just 'summarize' without a noun. This is a minor deviation from an otherwise consistent pattern.
With 3 tools, the server is well-scoped for an expense tracker. Each tool serves a necessary and distinct function without unnecessary bloat.
The server provides create (add), read (list), and aggregate (summarize) functionality, but lacks update and delete operations. This is a notable gap for a complete expense tracking lifecycle.