Skip to main content
Glama
Python-Blade

Expense Tracker MCP Server

by Python-Blade
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

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
add_expenseB
Add a new expense to the tracker.

Args:
    amount: The cost of the expense.
    category: The category of the expense (e.g., Food, Transport, Rent).
    description: A brief description of what was purchased.
    time: The time when the expense occured down to the day(default is current time).
delete_expenseC
Delete an expense by its ID.

Args:
    expense_id: The ID of the expense to delete.
list_expensesB

List all expenses recorded in the database. Returns a formatted string of expenses.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

B3.3/5.0

Scored across 3 tools

Disambiguation5/5

add_expense, delete_expense, and list_expenses target clearly distinct operations on the same resource. There is no meaningful overlap or ambiguity between them.

Naming Consistency5/5

All tools follow a consistent snake_case verb_noun pattern: add_expense, delete_expense, list_expenses. The plural in list_expenses is natural for a list operation.

Tool Count4/5

Three tools is reasonable for a minimal expense tracker, and each tool has a clear purpose. However, the surface is on the thin side for typical expense-tracking workflows.

Completeness3/5

The set covers add, delete, and list, but lacks update_expense and get_expense, which are notable gaps for correcting or inspecting individual records. Reporting operations like totals or filtering by category/date are also absent.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources