Skip to main content
Glama
akutishevsky

LunchMoney MCP Server

delete_transaction_group

Remove a transaction group or individual transaction from your LunchMoney financial data by specifying its ID to maintain accurate records.

Instructions

Delete a transaction group or a single transaction.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
inputYes

Implementation Reference

  • Handler function that performs DELETE request to Lunchmoney API to delete transaction group by ID.
    async ({ input }) => {
        const { baseUrl, lunchmoneyApiToken } = getConfig();
    
        const response = await fetch(
            `${baseUrl}/transactions/group/${input.transaction_id}`,
            {
                method: "DELETE",
                headers: {
                    Authorization: `Bearer ${lunchmoneyApiToken}`,
                },
            }
        );
    
        if (!response.ok) {
            return {
                content: [
                    {
                        type: "text",
                        text: `Failed to delete transaction group: ${response.statusText}`,
                    },
                ],
            };
        }
    
        return {
            content: [
                {
                    type: "text",
                    text: "Transaction group deleted successfully",
                },
            ],
        };
    }
  • Zod input schema defining transaction_id as a required number.
    {
        input: z.object({
            transaction_id: z
                .number()
                .describe("ID of the transaction group to delete"),
        }),
    },
  • Registration of the delete_transaction_group tool with server.tool, including description, schema, and inline handler.
        "delete_transaction_group",
        "Delete a transaction group or a single transaction.",
        {
            input: z.object({
                transaction_id: z
                    .number()
                    .describe("ID of the transaction group to delete"),
            }),
        },
        async ({ input }) => {
            const { baseUrl, lunchmoneyApiToken } = getConfig();
    
            const response = await fetch(
                `${baseUrl}/transactions/group/${input.transaction_id}`,
                {
                    method: "DELETE",
                    headers: {
                        Authorization: `Bearer ${lunchmoneyApiToken}`,
                    },
                }
            );
    
            if (!response.ok) {
                return {
                    content: [
                        {
                            type: "text",
                            text: `Failed to delete transaction group: ${response.statusText}`,
                        },
                    ],
                };
            }
    
            return {
                content: [
                    {
                        type: "text",
                        text: "Transaction group deleted successfully",
                    },
                ],
            };
        }
    );
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states the destructive action 'Delete' but lacks critical details: whether deletion is permanent or reversible, required permissions, confirmation prompts, or error handling. This is inadequate for a mutation tool with zero annotation coverage.

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?

The description is a single, efficient sentence with zero wasted words. It's front-loaded with the core action and resource, making it easy to parse quickly without unnecessary elaboration.

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 destructive mutation tool with no annotations, no output schema, and low parameter coverage, the description is incomplete. It fails to address critical aspects like return values, side effects, error cases, or how it differs from similar deletion tools, leaving significant gaps for agent understanding.

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 0%, and the description doesn't compensate by explaining parameters. It mentions 'transaction group or a single transaction', but the schema only has 'transaction_id' with minimal description. The discrepancy between description (group/single) and schema (single ID) creates confusion without clarification.

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 clearly states the verb 'Delete' and specifies the resource as 'transaction group or a single transaction', making the purpose unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'delete_category' or 'force_delete_category', which prevents a perfect score.

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?

The description provides no guidance on when to use this tool versus alternatives. There's no mention of prerequisites, conditions for use, or comparisons with related tools like 'delete_category' or 'unsplit_transactions', leaving the agent without context for selection.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/akutishevsky/lunchmoney-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server