Skip to main content
Glama
moneywiz-mcp

moneywiz-mcp

by kyledh

moneywiz_update_transaction

Idempotent

Update an existing MoneyWiz transaction by setting only the fields that need changes; any omitted fields retain their current values.

Instructions

Change a transaction. Fields left out keep their current values.

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": {
      "transaction_id": "<transaction_id>"
    },
    "name": "moneywiz_update_transaction"
  }
}

Input Schema

NameRequiredDescriptionDefault
feeNo
dateNo
memoNo
tagsNoTag names or ids; unknown names are created
payeeNo
amountNo
accountNo
categoriesNoOne category ("Food/Coffee" or its id), or a split as [{"category": "Food/Coffee", "amount": "10.00"}, ...] adding up to the amount
descriptionNo
transfer_toNo
receive_dateNo
cheque_numberNo
exchange_rateNo
transaction_idYes
original_amountNo
transfer_amountNo
original_currencyNo
transfer_exchange_rateNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare non-read-only, idempotent, non-destructive, closed-world behavior. The description adds genuine value by disclosing merge/partial-update semantics, but it omits other behavioral facts an 18-parameter mutation tool needs: what happens on invalid ids, whether category splits must sum to the amount, side effects on linked transfers, or error surfacing.

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 short sentences, front-loaded with the action and immediately followed by the key constraint. Nothing is wasted or buried.

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 an 18-parameter mutation tool with 11% schema coverage and no output schema, the description is drastically under-specified. An agent could not confidently determine how to supply splits, transfers, or currency fields, or what to expect on failure, from this definition alone.

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 description coverage is only 11% across 18 parameters, so the description is expected to compensate and largely does not — it names no parameters at all. The generic 'fields left out keep current values' rule implies all fields are optional overrides, but it gives no meaning for ambiguous fields such as original_amount, transfer_amount, transfer_exchange_rate, or exchange_rate.

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 names a specific verb ('Change') and resource ('a transaction'), so the agent knows this is a mutation of an existing transaction rather than a create/delete/get. It does not explicitly contrast itself with siblings like moneywiz_create_transaction or moneywiz_set_transaction_status, which keeps it short of a 5.

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 statement of when to use this tool versus create_transaction, delete_transaction, or set_transaction_status. The only usable guidance is the partial-update rule ('Fields left out keep their current values'), which tells the agent it can pass a subset of fields but not when this tool is the right choice.

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