Money Lover MCP Server

Add Transaction

add_transaction

Create a new financial transaction in a wallet by specifying amount, category, date, and optional details like notes or related parties.

Instructions

Create a new transaction in a wallet.

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": {
      "walletId": "<walletId>",
      "categoryId": "<categoryId>",
      "amount": "<amount>",
      "date": "<date>"
    },
    "name": "add_transaction"
  }
}

Input Schema

Name	Required	Description
`walletId`	Yes	Wallet identifier
`categoryId`	Yes	Category identifier
`amount`	Yes	Transaction amount as string
`note`	No	Optional transaction note
`date`	Yes	Display date in YYYY-MM-DD format
`with`	No	Optional array of related parties

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.0.3Apr 19, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations, the description carries full burden but only states it 'creates' without disclosing behavioral traits. It doesn't mention permissions needed, whether it's idempotent, error handling, or what happens on success (e.g., returns transaction ID). This leaves significant 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 a single, efficient sentence with zero wasted words. It's front-loaded with the core action and resource, making it easy to parse quickly without unnecessary elaboration.

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?

For a mutation tool with 6 parameters, no annotations, and no output schema, the description is incomplete. It lacks behavioral context, usage guidance, and details on what the tool returns or how errors are handled, leaving the agent under-informed for proper invocation.

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

Parameters3/5

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

Schema description coverage is 100%, so parameters are documented in the schema. The description adds no additional meaning beyond implying 'transaction' creation, which aligns with the schema but doesn't clarify parameter interactions or business rules (e.g., amount format).

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 description clearly states the action ('Create') and resource ('new transaction in a wallet'), making the purpose evident. However, it doesn't differentiate from sibling tools like 'edit_transaction' or specify what constitutes a 'transaction' (e.g., expense, income).

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 is provided on when to use this tool versus alternatives like 'edit_transaction' or 'delete_transaction'. The description lacks context about prerequisites (e.g., needing an existing wallet/category) or typical use cases, offering minimal usage direction.

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