Skip to main content
Glama
AKSHAYBITLINGU

Expense Tracker MCP

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
}
extensions
{
  "io.modelcontextprotocol/ui": {}
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
read_expensesA

Read all expenses

add_expenseC

Add an expense

summarize_expensesA

Get total expenses between start_date and end_date (ISO format)

filter_by_categoryA

Get all expenses for a specific category

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.4/5.0

Scored across 4 tools

Disambiguation4/5

The tools are largely distinct: read_expenses returns all expenses, add_expense creates a new one, summarize_expenses aggregates by date range, and filter_by_category filters by category. There is minor overlap between read_expenses and filter_by_category, as the latter could be seen as a subset, but the descriptions clearly differentiate their purposes.

Naming Consistency4/5

All tool names follow a consistent snake_case convention with a verb prefix (read_, add_, summarize_, filter_). The only slight deviation is 'filter_by_category' which uses a preposition, but it still aligns with the overall verb_noun style.

Tool Count4/5

With 4 tools, the server is well-scoped for a basic expense tracker. Each tool serves a clear purpose, though the set feels slightly minimal for a domain that could benefit from update and delete operations.

Completeness3/5

The core operations of reading and adding expenses are covered, along with useful summaries and category filtering. However, there are notable gaps: no update or delete expense functionality, and filtering is only by category, not by date range (only totals via summarize). These omissions may limit agents that need full lifecycle management.

Maintenance

ActivityInactive
ResponsivenessNo issues