Skip to main content
Glama
akutishevsky

LunchMoney MCP Server

by akutishevsky
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

update_transaction

Idempotent

Update an existing transaction's details in LunchMoney by supplying writable fields. For split or grouped transactions, use the dedicated split/group tools instead.

Instructions

Update an existing transaction. Provide any subset of writable fields directly (the v2 API no longer wraps the body in a transaction envelope). Cannot modify split or grouped transactions; use the corresponding split/group tools instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
updateYesFields to update. Provide at least one writable field.
transaction_idYesID of the transaction to update.
update_balanceNoDefaults to true. Pass false to skip updating the associated manual account's balance.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.3
  2. Removedv1.0.2
  3. Changed7 schema fields changedv1.0.1
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / input
      Removed value: -{
-  "additionalProperties": false,
-  "properties": {
-    "debit_as_negative": {
-      "description": "Pass true if debits are provided as negative amounts",
-      "type": "boolean"
-    },
-    "skip_balance_update": {
-      "description": "Skip updating balance for assets/accounts",
-      "type": "boolean"
-    },
-    "transaction": {
-      "additionalProperties": false,
-      "description": "Transaction data to update",
-      "properties": {
-        "amount": {
-          "description": "Amount as string with up to 4 decimal places",
-          "type": "string"
-        },
-        "asset_id": {
-          "description": "Asset ID for manual accounts",
-          "type": "number"
-        },
-        "category_id": {
-          "description": "Category ID",
-          "type": "number"
-        },
-        "currency": {
-          "description": "Three-letter lowercase currency code",
-          "type": "string"
-        },
-        "date": {
-          "description": "Date in YYYY-MM-DD format",
-          "type": "string"
-        },
-        "external_id": {
-          "description": "External ID (max 75 characters)",
-          "type": "string"
-        },
-        "notes": {
-          "description": "Transaction notes",
-          "type": "string"
-        },
-        "payee": {
-          "description": "Payee name",
-          "type": "string"
-        },
-        "recurring_id": {
-          "description": "Recurring expense ID",
-          "type": "number"
-        },
-        "status": {
-          "description": "Transaction status",
-          "enum": [
-            "cleared",
-            "uncleared",
-            "pending"
-          ],
-          "type": "string"
-        },
-        "tags": {
-          "description": "Array of tag IDs",
-          "items": {
-            "type": "number"
-          },
-          "type": "array"
-        }
-      },
-      "type": "object"
-    },
-    "transaction_id": {
-      "description": "ID of the transaction to update",
-      "type": "number"
-    }
-  },
-  "required": [
-    "transaction_id",
-    "transaction"
-  ],
-  "type": "object"
-}
    • addedInput schema / properties / transaction_id
      Added value: +{
+  "description": "ID of the transaction to update.",
+  "type": "number"
+}
    • addedInput schema / properties / update
      Added value: +{
+  "additionalProperties": false,
+  "description": "Fields to update. Provide at least one writable field.",
+  "properties": {
+    "additional_tag_ids": {
+      "description": "Adds these tags to the existing transaction tags. Mutually exclusive with tag_ids.",
+      "items": {
+        "type": "number"
+      },
+      "type": "array"
+    },
+    "amount": {
+      "type": "number"
+    },
+    "category_id": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "currency": {
+      "maxLength": 3,
+      "minLength": 3,
+      "type": "string"
+    },
+    "custom_metadata": {
+      "anyOf": [
+        {
+          "additionalProperties": {},
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "date": {
+      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
+      "type": "string"
+    },
+    "external_id": {
+      "anyOf": [
+        {
+          "maxLength": 75,
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "manual_account_id": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "notes": {
+      "anyOf": [
+        {
+          "maxLength": 350,
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "payee": {
+      "maxLength": 140,
+      "type": "string"
+    },
+    "plaid_account_id": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "recurring_id": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "status": {
+      "enum": [
+        "reviewed",
+        "unreviewed"
+      ],
+      "type": "string"
+    },
+    "tag_ids": {
+      "description": "Replaces all existing tags on the transaction. Mutually exclusive with additional_tag_ids.",
+      "items": {
+        "type": "number"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}
    • addedInput schema / properties / update_balance
      Added value: +{
+  "description": "Defaults to true. Pass false to skip updating the associated manual account's balance.",
+  "type": "boolean"
+}
    • changedInput schema / required
      Previous value: -[
-  "input"
-]New value: +[
+  "transaction_id",
+  "update"
+]
  4. First observedv1.0.0

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already indicate idempotency (idempotentHint: true). Description adds useful constraint about split/group transactions but no further behavioral traits (e.g., response format, error behavior). Adequate but not exceptional.

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, no fluff, front-loaded with the core action. Every word earns its place.

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

Completeness4/5

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

Given the tool's complexity (nested update object, high schema coverage but no output schema), the description covers the key constraint and API version change. Missing a note on return value, but output schema is absent, so minor gap.

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 the description does not need to add much. It mentions 'writable fields' and the v2 envelope change, but does not explain individual parameters beyond what the schema provides. Baseline 3 is appropriate.

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 the verb (update) and resource (existing transaction), and distinguishes from siblings by explicitly mentioning that split or grouped transactions cannot be modified and should use corresponding tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides direct when-to-use and when-not-to-use guidance: cannot modify split/grouped transactions, and directs to use split/group tools instead. No ambiguity.

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

Deploy Server

Other Tools