Skip to main content
Glama
samu187

expenses-tracker-mcp

by samu187

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
run_readonly_sqlC

Run a guarded read-only SQL query and return columns plus rows.

list_pending_groupsC

List pending transactions grouped by counterparty.

list_transactionsA

List transactions using optional month, account, counterparty, and amount filters.

list_accountsB

List accounts, optionally filtered by account group name.

update_transactions_accountC

Assign specific transactions to an account.

bulk_update_by_filterC

Assign all transactions matching a filter to an account, or preview with dry_run.

get_classification_summaryB

Summarize transactions grouped by counterparty, account, or account group.

create_accountB

Create an account in an existing account group.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.1/5.0

Scored across 8 tools

Disambiguation4/5

Tools are mostly distinct: raw SQL, list operations, update operations, and create account each target a unique action. However, list_pending_groups and get_classification_summary both group transactions, and update_transactions_account vs bulk_update_by_filter could be confused, though descriptions clarify the difference.

Naming Consistency4/5

The majority follow a clear verb_noun pattern (list_, create_, update_, get_). Minor deviations like bulk_update_by_filter and run_readonly_sql are still readable and consistent in style, so the overall pattern is predictable.

Tool Count5/5

8 tools is well-scoped for an expense tracking server. Each tool serves a clear purpose in querying, updating, or creating accounts, with no redundant or missing trivialities.

Completeness3/5

The surface covers listing, classification, account creation, and transaction updates, but lacks a create_transaction tool, which is a core operation for an expense tracker. Also missing account update/delete, leaving notable gaps for full lifecycle management.

Maintenance

ActivityMaintained
ResponsivenessNo issues