Local MCP Server Expense Tracker
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 expense to database |
| list_expensesA | Get all expenses from database |
| edit_expenseC | Edit expense in database |
| delete_expenseC | Delete expense from database |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a distinct operation (add, delete, edit, list) with no overlap, making it easy for an agent to select the correct one.
All tool names follow a consistent verb_noun pattern using snake_case, which is predictable and readable.
Four tools cover the core CRUD operations for an expense tracker; the count is appropriate and not excessive.
The set provides essential create, read (list), update, and delete operations, but lacks a single-expense retrieval tool, which is a minor gap.