Smart Expense Management MCP

Overview Schema Source Related Servers Discussions Admin

search_expenses

Search and analyze your expenses using natural language queries. Find specific transactions, view spending summaries, and filter by date, amount, merchant, and more.

Instructions

Natural language expense search.

Claude should use this when the user asks conversational questions about their spending.

Examples: "How much did I spend on food this month?" "Show me Domino's expenses" "All UPI payments above ₹500 in June" "What did I spend at Girnar trip?" "Show my expensive purchases in 2026"

Returns both the matching expenses AND a quick summary (total, count, avg).

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": {
      "query": "<query>"
    },
    "name": "search_expenses"
  }
}

Input Schema

Name	Required	Description	Default
`tags`	No
`year`	No
`month`	No
`query`	Yes
`event_id`	No
`merchant`	No
`max_amount`	No
`min_amount`	No
`category_id`	No
`payment_method`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 14, 2026

TDQS

A3.7/5.0

Behavior3/5

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

No annotations are provided, so the description carries full burden. It mentions returns both matching expenses and a summary (total, count, avg), which adds transparency. However, it does not disclose potential side effects, permissions, or limits like pagination.

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 description is concise at a few lines with embedded examples. It is front-loaded with the key purpose. The examples add value without unnecessary repetition.

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?

Given 10 parameters with no schema descriptions and no annotations, the description is moderately complete for the primary use case but fails to explain the majority of parameters or edge cases. The return format is partially described.

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 coverage is 0%, and the description does not explain any parameter individually. It assumes the query parameter handles natural language but ignores tags, year, month, etc. With 10 parameters, this is insufficient guidance.

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 it is for 'Natural language expense search' and provides multiple examples showing conversational queries. It distinguishes from sibling tools like list_expenses and get_expense by emphasizing natural language input.

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

Usage Guidelines4/5

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

The description explicitly says 'Claude should use this when the user asks conversational questions about their spending,' giving clear context. It does not mention when not to use or alternatives, but the sibling tools imply non-conversational search options.

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