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: adding, listing, and summarizing expenses. There is no overlap or ambiguity.
Two tools follow verb_noun pattern consistently, but summarizemissing a noun and pluralization differs (expense vs expenses), which is a minor deviation.
Three tools is borderline low for an expense tracker; while core read and create are covered, it feels slightly under-scoped.
Notable missing operations: update and delete for expenses, and no category management. This creates significant gaps in typical expense tracking workflows.