Skip to main content
Glama
mayankchugh-learning

expense-mcp

add_expense

Record an expense with date, amount, and category. Optionally add subcategory and note, and get the new expense ID.

Instructions

Insert one expense row and return the new row id.

Args: date: Calendar date of the expense, preferably YYYY-MM-DD. amount: Monetary amount (positive number). category: High-level label (e.g. food, transport). subcategory: Optional finer grouping (default empty string). note: Optional free text (default empty string).

Returns: A dict with status "ok" and id set to the new SQLite INTEGER PRIMARY KEY, or None if the driver does not expose it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateYes
noteNo
amountYes
categoryYes
subcategoryNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

The description discloses the return value behavior, including the possibility of None. It also provides a date format hint. However, it does not mention any side effects, authentication needs, or rate limits, though for a simple insert tool this is adequate. Annotations are missing, so the description carries full burden.

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

Conciseness5/5

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

The description is well-structured with 'Args' and 'Returns' sections. Every sentence adds value, and there is no redundant or extraneous text. It is appropriately sized for the tool's complexity.

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

Completeness5/5

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

The description covers all necessary information: what the tool does, how to use each parameter, and what to expect as output. It is complete for a tool of this complexity, especially given the presence of an output schema (even if not provided in the input, the description explains it).

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

Parameters5/5

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

With 0% schema description coverage, the description fully compensates by providing semantic meaning for each parameter: date format, amount as positive monetary value, category as high-level label, and optional fields with defaults. This exceeds the bare schema definition.

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

Purpose5/5

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

The description clearly states the verb 'Insert', the resource 'expense row', and the return value 'new row id'. It distinguishes itself from sibling tools 'list_expenses' and 'summarize' by being the only write operation.

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

Usage Guidelines3/5

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

The description implies usage for adding an expense, but does not provide explicit guidance on when to use this tool versus alternatives, nor does it mention any prerequisites or when not to use.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mayankchugh-learning/local-expense-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server