Expense Tracker MCP Server

Overview Schema Source Related Servers Discussions Admin

add_expense

Add a new expense entry with required amount and category, plus optional date (defaults to current IST), note, and subcategory.

Instructions

Add a new expense entry to the database. If date is not provided, it defaults to current IST date.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "amount": "<amount>",
      "category": "<category>"
    },
    "name": "add_expense"
  }
}

Input Schema

Name	Required	Description	Default
`date`	No
`note`	No
`amount`	Yes
`category`	Yes
`subcategory`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 10, 2026

TDQS

A3.6/5.0

Behavior3/5

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

No annotations are provided, so the description must carry the full burden. It discloses a useful behavioral trait (date defaults to current IST date), but does not mention return values, validation rules, or any side effects. This adds some value but leaves notable gaps for a mutation tool.

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 two short sentences with no redundancy. The purpose is front-loaded, and the date default is stated efficiently. Every word earns its place.

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?

For a simple create tool with an output schema, the description covers the core purpose and one key default. However, it lacks usage guidance and parameter explanations, which could leave an agent uncertain about how to properly construct inputs or when this tool is appropriate.

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

Parameters2/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. It only explains the date parameter's default behavior, leaving amount, category, note, and subcategory unexplained. The names are somewhat self-explanatory, but the description adds minimal meaning beyond the schema itself.

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 'Add' and the resource 'expense entry', making its purpose unambiguous. It is easily distinguished from sibling tools list_expenses and summarize, which involve reading and analyzing rather than creating.

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?

No explicit guidance is given on when to use this tool versus alternatives. The description implies usage by describing the action, and the date default provides a usage nuance, but there is no mention of exclusions or comparison to list_expenses or summarize.

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

Deploy Server