Skip to main content
Glama
Python-Blade

Expense Tracker MCP Server

by Python-Blade
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

add_expense

Records a new expense with amount, category, and optional details like description and time. Use for tracking personal or business spending.

Instructions

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).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
timeNo2026-09-13T06:15:40.468342
amountYes
categoryYes
descriptionNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full behavioral burden. It implies a write operation but says nothing about persistence, duplicate handling, required permissions, or what happens to existing data. Only the time default ('default is current time') adds any behavioral context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The docstring is front-loaded with the purpose and then lists parameters compactly. It is slightly boilerplate ('Args:') and contains a typo ('occured'), but no sentence is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be explained, and parameters are covered. However, for a mutation tool with zero annotations, the description omits any note on side effects, permissions, or duplicate behavior, leaving a meaningful gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate, and it does: it documents all four parameters, gives concrete category examples (Food, Transport, Rent), and clarifies the time default. This is genuine added meaning beyond the bare schema titles.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The first line gives a clear verb+resource ('Add a new expense to the tracker'), which an agent can distinguish from delete_expense and list_expenses without opening a schema. It does not, however, explicitly name or contrast those siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this tool versus delete_expense or list_expenses, nor any prerequisites or exclusions. Usage is only implied by the verb 'Add'.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools