Skip to main content
Glama
moneylover-mcp

moneylover-mcp

Add Transaction

add_transaction

Create a new transaction in a specified wallet using a wallet or global category ID, with amount, date, and optional note or related parties.

Instructions

Create a new transaction in a wallet. categoryId may be a wallet-specific id from get_categories or a global category id; it is translated to the global id the current API expects.

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

NameRequiredDescriptionDefault
dateYesDisplay date in YYYY-MM-DD format
noteNoOptional transaction note
withNoOptional array of related parties
tokenNoJWT token returned by login, or derived from environment credentials
amountYesTransaction amount
walletIdYesWallet identifier
categoryIdYesCategory identifier (wallet-specific or global)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full behavioral burden. It discloses one real behavior beyond the schema — that categoryId is translated from a wallet-specific to a global id — but says nothing about authentication requirements (a token param exists), whether writes are idempotent, or what happens on invalid category/wallet combinations. For a mutation tool with zero annotation coverage, this is thin.

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?

Two sentences, front-loaded with the action, followed by the one non-obvious semantic caveat. Nothing is padded and nothing repeats the title.

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 7-parameter mutation with no annotations and no output schema, the description covers purpose and the categoryId nuance but omits auth expectations, validation behavior, and whether the created transaction (or its id) is returned. An agent can call it, but with avoidable uncertainty.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, and the description earns above that by explaining that categoryId accepts either a wallet-specific id from get_categories or a global id and is normalized internally. That is genuine meaning the schema's "wallet-specific or global" phrasing only hints at.

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?

States a specific verb and resource ("Create a new transaction in a wallet"), which clearly separates it from the read-oriented siblings (get_transactions, get_wallets, get_categories). It stops short of naming a sibling explicitly, but the create-vs-read distinction is unmistakable.

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?

Usage is only implied: the agent infers this is the tool for recording a new transaction, and the description usefully points to get_categories as the source of categoryId. There is no explicit when-not guidance, no mention of prerequisites such as login/token, and no note about duplicate handling.

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