Expense Tracker MCP
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| add_expenseC | Add a new expense entry to the database. |
| list_expensesB | 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 when selecting between them.
Mostly follows a verb_noun pattern (add_expense, list_expenses), but 'summarize' lacks a noun suffix, creating a minor inconsistency. Still predictable and readable.
Three tools are well-scoped for a simple expense tracker and each earns its place. No bloat or deficiency.
Core expense tracking operations are covered (create, read, summarize), but missing update/delete functionality is a notable gap. Agents can work around this for read-heavy use cases.