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_expenseD | – |
| list_expensesD | – |
| summarizeA | Summarize expenses between two dates, providing a detailed analysis, financial advice, and a visualization graph. |
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 an expense, listing expenses, and summarizing/analyzing them. There is no overlap in their core functions, making it easy for an agent to choose the right tool.
Most tools follow the verb_noun pattern (add_expense, list_expenses), but 'summarize' lacks an object, deviating from the pattern. There is also a minor singular/plural inconsistency between 'expense' and 'expenses'. Overall the convention is readable and predictable.
With only three tools, the set is minimal but appropriate for a simple expense tracker. The count is not excessively thin (like 1-2) and stays within a reasonable scope, though one could imagine additional tools for management.
The server covers creating and reading expenses, plus a summary/analysis function, but lacks update and delete operations. For an expense tracker, the inability to modify or remove expenses is a notable gap that agents would have to work around.