Skip to main content
Glama
akutishevsky

LunchMoney MCP Server

get_single_transaction

Read-only

Retrieve detailed information for a specific transaction, including plaid metadata, custom metadata, files, and children for split or group parents. Provides complete transaction details not available in bulk queries.

Instructions

Get details of a specific transaction. The response always includes plaid_metadata, custom_metadata, files, and (for split or group parents) the children array — none of which are returned by default in get_transactions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
transaction_idYesID of the transaction to retrieve.

Implementation Reference

  • Registration of the 'get_single_transaction' tool via server.registerTool(), including its description, inputSchema (transaction_id), and readOnlyHint annotation.
    server.registerTool(
        "get_single_transaction",
        {
            description:
                "Get details of a specific transaction. The response always includes plaid_metadata, custom_metadata, files, and (for split or group parents) the children array — none of which are returned by default in get_transactions.",
            inputSchema: {
                transaction_id: z.coerce
                    .number()
                    .describe("ID of the transaction to retrieve."),
            },
            annotations: {
                readOnlyHint: true,
            },
        },
        async ({ transaction_id }) => {
            try {
                const response = await api.get(
                    `/transactions/${transaction_id}`,
                );
    
                if (!response.ok) {
                    return handleApiError(
                        response,
                        "Failed to get transaction",
                    );
                }
    
                return dataResponse(await response.json());
            } catch (error) {
                return catchError(error, "Failed to get transaction");
            }
        },
    );
  • Handler function for 'get_single_transaction' that calls GET /transactions/{transaction_id} and returns the response data.
    async ({ transaction_id }) => {
        try {
            const response = await api.get(
                `/transactions/${transaction_id}`,
            );
    
            if (!response.ok) {
                return handleApiError(
                    response,
                    "Failed to get transaction",
                );
            }
    
            return dataResponse(await response.json());
        } catch (error) {
            return catchError(error, "Failed to get transaction");
        }
    },
  • Input schema for the tool: transaction_id (coerced number) describing the ID of the transaction to retrieve.
    inputSchema: {
        transaction_id: z.coerce
            .number()
            .describe("ID of the transaction to retrieve."),
    },
  • Imports for utility helpers used by the handler: api, dataResponse, handleApiError, catchError from '../api.js'.
    import {
        api,
        dataResponse,
        successResponse,
        handleApiError,
        catchError,
        errorResponse,
    } from "../api.js";
  • src/index.ts:28-28 (registration)
    Top-level registration call: registerTransactionTools(server) which registers all transaction tools including get_single_transaction.
    registerTransactionTools(server);
Behavior4/5

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

Annotations indicate readOnlyHint: true, and the description does not contradict this. It adds value by detailing the extra response fields beyond the default list endpoint. It does not mention any side effects or permissions, which is acceptable for a read operation.

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 with no unnecessary words. The first sentence gives the purpose, the second explains the key distinction. 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 simplicity (one parameter, read-only) and lack of output schema, the description adequately covers what the tool does and what it returns. It could mention prerequisites (e.g., transaction must exist), but that is implied.

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?

The input schema has 100% coverage with a clear description for the sole parameter 'transaction_id'. The description adds no additional information about parameters beyond the schema, so 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 ('Get') and resource ('specific transaction'), and explicitly distinguishes this tool from the sibling get_transactions by listing extra fields returned.

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?

The description provides explicit guidance on when to use this tool (when needing plaid_metadata, custom_metadata, files, children) and implicitly when not to (use get_transactions for basic info). It names the alternative sibling.

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