Skip to main content
Glama
neev-25

Smart Expense Management MCP

by neev-25

create_expense

Record a new expense by specifying title, amount, and date, with optional category, merchant, and payment method.

Instructions

Add a new expense.

Examples:

  • "₹450 at Domino's for dinner, paid via UPI, category Food"

  • "Flight ticket ₹3500 for Rahul, category Travel"

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagsNo
notesNo
titleYes
amountYes
currencyNoINR
locationNo
merchantNo
category_idNo
descriptionNo
receipt_urlNo
expense_dateYes
payment_methodNoCash
subcategory_idNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It only states 'Add a new expense' without mentioning side effects, permissions, or response format beyond what the output schema implies.

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

Conciseness3/5

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

The description is brief but lacks structure. The examples are useful but the text is minimal and does not fully cover the tool's purpose.

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

Completeness2/5

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

Given 13 parameters and no schema descriptions or annotations, the description is insufficient for an agent to use the tool correctly. It omits parameter details and usage context.

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%, yet the description offers only examples without clarifying parameter meanings or constraints. Many optional parameters are left unexplained.

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 'Add a new expense' with concrete examples that differentiate it from sibling tools like 'add_recurring' or 'add_event_expense'.

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?

No guidance on when to use this tool versus alternatives. The examples show usage patterns but do not explicitly state when not to use or suggest sibling tools.

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/neev-25/expense-manager-mcp'

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