Skip to main content
Glama
akutishevsky

LunchMoney MCP Server

by akutishevsky
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

create_transaction_group

Combine 2-500 existing transactions into a new grouped transaction, hiding the originals from regular lists. Access them as children of the group to keep related entries together.

Instructions

Create a transaction group from 2-500 existing transactions. Source transactions are hidden from get_transactions and accessible via the new group's children (set include_children=true on get_single_transaction). Cannot include split or recurring transactions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idsYesIDs of existing transactions to group together.
dateYesDate for the new grouped transaction (YYYY-MM-DD).
notesNo
payeeYesPayee for the new grouped transaction.
statusNoStatus for the new grouped transaction. Defaults to reviewed.
tag_idsNoTag IDs to apply to the new group.
category_idNoCategory for the group. If unset and all children share a category, the group inherits it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.3
  2. Removedv1.0.2
  3. Changed11 schema fields changedv1.0.1
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / category_id
      Added value: +{
+  "description": "Category for the group. If unset and all children share a category, the group inherits it.",
+  "type": [
+    "number",
+    "null"
+  ]
+}
    • addedInput schema / properties / date
      Added value: +{
+  "description": "Date for the new grouped transaction (YYYY-MM-DD).",
+  "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
+  "type": "string"
+}
    • addedInput schema / properties / ids
      Added value: +{
+  "description": "IDs of existing transactions to group together.",
+  "items": {
+    "type": "number"
+  },
+  "maxItems": 500,
+  "minItems": 2,
+  "type": "array"
+}
    • removedInput schema / properties / input
      Removed value: -{
-  "additionalProperties": false,
-  "properties": {
-    "category_id": {
-      "description": "Category ID for the group",
-      "type": "number"
-    },
-    "date": {
-      "description": "Date in YYYY-MM-DD format",
-      "type": "string"
-    },
-    "notes": {
-      "description": "Notes for the group",
-      "type": "string"
-    },
-    "payee": {
-      "description": "Payee name for the group",
-      "type": "string"
-    },
-    "tags": {
-      "description": "Array of tag IDs for the group",
-      "items": {
-        "type": "number"
-      },
-      "type": "array"
-    },
-    "transaction_ids": {
-      "description": "Array of transaction IDs to group",
-      "items": {
-        "type": "number"
-      },
-      "type": "array"
-    }
-  },
-  "required": [
-    "date",
-    "payee",
-    "transaction_ids"
-  ],
-  "type": "object"
-}
    • addedInput schema / properties / notes
      Added value: +{
+  "anyOf": [
+    {
+      "maxLength": 350,
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}
    • addedInput schema / properties / payee
      Added value: +{
+  "description": "Payee for the new grouped transaction.",
+  "maxLength": 140,
+  "type": "string"
+}
    • addedInput schema / properties / status
      Added value: +{
+  "description": "Status for the new grouped transaction. Defaults to reviewed.",
+  "enum": [
+    "reviewed",
+    "unreviewed"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / tag_ids
      Added value: +{
+  "description": "Tag IDs to apply to the new group.",
+  "items": {
+    "type": "number"
+  },
+  "type": "array"
+}
    • changedInput schema / required
      Previous value: -[
-  "input"
-]New value: +[
+  "ids",
+  "date",
+  "payee"
+]
  4. First observedv1.0.0

TDQS

A4.6/5.0
Behavior5/5

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

The description reveals that source transactions become hidden from get_transactions and are accessible via the group's children, which is a behavioral side effect not captured by annotations or schema. It also states restrictions on split/recurring transactions, adding significant transparency.

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?

Three well-structured sentences: first defines core purpose, second explains behavioral effect, third states restrictions. No unnecessary words, each sentence adds value.

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?

The description covers key behavioral aspects and restrictions. While it lacks return value details and error scenarios, the absence of an output schema and the complexity of the tool make this acceptable. It is adequately complete for an agent.

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?

With 86% schema coverage, the description adds value beyond the schema by explaining constraints for ids (2-500, no split/recurring) and inheritance behavior for category_id. It does not repeat schema details but enhances understanding.

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 action (create) and resource (transaction group) with specific constraints (2-500 existing transactions). It effectively distinguishes from sibling tools like create_transactions and delete_transaction_group.

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

Usage Guidelines4/5

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

It provides clear context on when to use (grouping existing transactions) and restrictions (cannot include split or recurring). It also explains how to access the group's children, but lacks explicit alternatives for when not to use.

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