Skip to main content
Glama
Soumya26Agrawal

Expense Tracker MCP Server

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": true
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
add_expenseC

Add a new expense entry to the database.

list_expensesC

List expense entries within an inclusive date range.

summarizeB

Summarize expenses by category within an inclusive date range.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription
categories

TDQS

B3.2/5.0

Scored across 3 tools

Disambiguation5/5

The three tools have clearly distinct purposes: add_expense creates a record, list_expenses retrieves raw records, and summarize aggregates by category. There is no overlap or ambiguity between them.

Naming Consistency4/5

All tools use lowercase snake_case and a verb-first pattern (add_, list_, summarize). The only minor inconsistency is that 'summarize' omits the explicit noun 'expenses' that the other two include, but it remains predictable and readable.

Tool Count4/5

Three tools is a reasonable size for a focused expense tracker. It is slightly minimal but each tool serves a distinct core function (insert, query, aggregate), so the count feels appropriate rather than inadequate.

Completeness3/5

The surface covers basic recording, viewing, and summarizing expenses, but lacks update and delete operations, which are common expected capabilities in a data management domain. This is a notable gap that agents cannot easily work around.

Maintenance

ActivitySlowing
ResponsivenessNo issues