Finance Tracking 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
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| add_expenseB | Add a new expense entry to the database. |
| edit_expenseB | Edit an existing expense by ID. Only pass the fields you want to change. |
| expense_summaryA | Get a spending summary, optionally filtered by category and/or month. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| get_categories |
TDQS
Scored across 3 tools
Each tool serves a clearly distinct purpose: summarizing expenses, adding new ones, and editing existing ones. There is no overlap or ambiguity in their functions.
Two tools follow a verb_noun pattern (add_expense, edit_expense), while expense_summary deviates slightly as a noun-first name. This minor inconsistency does not hinder readability.
With only 3 tools, the server is well-scoped for a focused expense tracking purpose. Each tool earns its place with no redundancy or excess.
The server covers add, edit, and summary, but lacks a delete operation and a way to retrieve individual expense details. This represents a notable gap in lifecycle coverage.