expense-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
} |
| 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_expenseA | Insert one expense row and return the new row id. Args:
date: Calendar date of the expense, preferably Returns:
A dict with |
| list_expensesA | Return all expenses with Rows are ordered by Args:
start_date: Range start, Returns:
List of dicts with keys |
| summarizeA | Aggregate total spend per category over a date range. Args:
start_date: Range start, Returns:
List of dicts with keys |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| categories | MCP resource: raw contents of ``categories.json`` beside ``main.py``. The file is read on each request so edits apply without restarting the server. Returns UTF-8 text; MIME type is ``application/json``. Raises: FileNotFoundError: If ``categories.json`` does not exist. |
TDQS
Scored across 3 tools
Each tool has a distinct purpose: adding an expense, listing expenses by date range, and summarizing spending by category. There is no overlap or ambiguity.
All tool names follow a consistent verb_noun pattern using snake_case (add_expense, list_expenses, summarize). The pattern is predictable and clear.
With 3 tools, the server is well-scoped for its purpose of basic expense tracking. The count is neither too few nor too many for the apparent domain.
The tool surface covers adding, listing, and summarizing expenses, which covers core use cases. However, it lacks update and delete operations, which are minor gaps for complete lifecycle management.