Skip to main content
Glama
moneywiz-mcp

moneywiz-mcp

by kyledh

moneywiz_create_transaction

Create an expense, income, transfer, or refund in MoneyWiz and return the saved transaction with its assigned ID and ledger details.

Instructions

Add a transaction and return it as MoneyWiz saved it.

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": {
      "account": "<account>",
      "kind": "<kind>",
      "amount": "<amount>",
      "date": "<date>"
    },
    "name": "moneywiz_create_transaction"
  }
}

Input Schema

NameRequiredDescriptionDefault
feeNo
dateYesYYYY-MM-DD (local day) or ISO 8601 timestamp
kindYes
memoNo
tagsNoTag names or ids; unknown names are created
payeeNo
amountYesPositive decimal string, e.g. "12.50"
statusNopending or cleared; default follows the account
accountYesAccount id, or its exact name
refund_ofNoRefunds: id of the expense being refunded
categoriesNoOne category ("Food/Coffee" or its id), or a split as [{"category": "Food/Coffee", "amount": "10.00"}, ...] adding up to the amount
descriptionNo
transfer_toNoTransfers: destination account
receive_dateNoTransfers: when the money arrives
cheque_numberNo
exchange_rateNoAccount currency per unit of original_currency
original_amountNoAmount in the foreign currency paid
transfer_amountNoTransfers: amount received, when currencies differ
original_currencyNoThat currency's 3-letter code
transfer_exchange_rateNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=false, so the safety profile is covered. The description adds only that the saved record is echoed back, and says nothing about the non-idempotent duplicate-on-retry risk or the side effect of creating unknown tags/payees/categories that the schema hints at.

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?

A single front-loaded sentence with no filler. It is efficient, though the brevity borders on under-specification for a 20-parameter mutation tool.

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 create tool with 20 parameters, no output schema, and conditional field requirements by kind, one sentence is not enough. Nothing tells the agent which optional fields matter for transfers versus refunds, or what the returned object contains.

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?

With 20 parameters and only 65% schema description coverage, the description carries real burden here but contributes nothing about any parameter. It does not explain the kind-dependent fields (transfer_to, refund_of, exchange_rate) or the split-category form, leaving the agent to reverse-engineer them from the schema.

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 ('Add a transaction') and adds that the saved record is returned, which distinguishes it from the get/update/delete transaction siblings. It stops short of naming or contrasting any sibling explicitly.

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?

There is no guidance on when to use this versus moneywiz_update_transaction or moneywiz_set_transaction_status, and no prerequisites (e.g. account must exist, categories/payees are auto-created). The agent must infer all routing from the name alone.

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