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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| add_expenseD | – |
| list_expensesC | list all expenses within an inclusive date range |
| summarizeD | – |
| updateB | Update an expense.Only provided fields will be updated. |
| deleteC | Delete expenses based on any column criteria. like id,date,category,subcategory,amount,note,start_date,end_date |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| categories | Get available expense categories |
TDQS
Scored across 5 tools
Most tools have distinct purposes: add_expense, list_expenses, and update are clearly differentiated. However, 'summarize' lacks a description, which could cause confusion about its exact function relative to list_expenses, potentially leading to misselection if it overlaps in providing expense overviews.
The naming is mixed: add_expense, list_expenses, and summarize follow a verb_noun pattern, but 'delete' and 'update' are standalone verbs without nouns, breaking consistency. This deviation makes the set less predictable, though the names are still readable overall.
With 5 tools, the count is well-scoped for an expense tracker server, covering core operations like adding, listing, updating, deleting, and summarizing expenses. Each tool earns its place without feeling excessive or insufficient for the domain.
The toolset provides good CRUD coverage with add, list, update, and delete, along with a summarize function for analytics. A minor gap exists in the lack of descriptions for add_expense and summarize, which could hinder agent understanding, but core lifecycle operations are present and workable.