Skip to main content
Glama
akutishevsky

LunchMoney MCP Server

trigger_plaid_fetch

Fetch the latest financial data from Plaid to update transaction records and account balances in LunchMoney. This experimental process may take up to 5 minutes to complete.

Instructions

Trigger a fetch of latest data from Plaid (Experimental). Note that fetching may take up to 5 minutes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The asynchronous handler function for the 'trigger_plaid_fetch' tool. It sends a POST request to the LunchMoney API endpoint '/plaid_accounts/fetch' to trigger fetching the latest data from Plaid accounts. Returns a success or error message in MCP content format.
    async () => {
        const { baseUrl, lunchmoneyApiToken } = getConfig();
        
        const response = await fetch(`${baseUrl}/plaid_accounts/fetch`, {
            method: "POST",
            headers: {
                Authorization: `Bearer ${lunchmoneyApiToken}`,
            },
        });
    
        if (!response.ok) {
            return {
                content: [
                    {
                        type: "text",
                        text: `Failed to trigger Plaid fetch: ${response.statusText}`,
                    },
                ],
            };
        }
    
        return {
            content: [
                {
                    type: "text",
                    text: "Plaid fetch triggered successfully. Fetching may take up to 5 minutes.",
                },
            ],
        };
    }
  • The server.tool registration for 'trigger_plaid_fetch', including the tool name, description, empty input schema, and the handler function. This is called within the registerPlaidAccountTools function.
    server.tool(
        "trigger_plaid_fetch",
        "Trigger a fetch of latest data from Plaid (Experimental). Note that fetching may take up to 5 minutes.",
        {},
        async () => {
            const { baseUrl, lunchmoneyApiToken } = getConfig();
            
            const response = await fetch(`${baseUrl}/plaid_accounts/fetch`, {
                method: "POST",
                headers: {
                    Authorization: `Bearer ${lunchmoneyApiToken}`,
                },
            });
    
            if (!response.ok) {
                return {
                    content: [
                        {
                            type: "text",
                            text: `Failed to trigger Plaid fetch: ${response.statusText}`,
                        },
                    ],
                };
            }
    
            return {
                content: [
                    {
                        type: "text",
                        text: "Plaid fetch triggered successfully. Fetching may take up to 5 minutes.",
                    },
                ],
            };
        }
    );
  • src/index.ts:30-30 (registration)
    Top-level call to registerPlaidAccountTools(server), which in turn registers the 'trigger_plaid_fetch' tool among others.
    registerPlaidAccountTools(server);
Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses key behavioral traits: the action is a fetch (implying read-only data retrieval), it's experimental (suggests potential instability), and it has a latency consideration ('up to 5 minutes'). However, it doesn't cover other important aspects like error handling, rate limits, idempotency, or what 'trigger' entails (e.g., async vs. sync).

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 highly concise and well-structured: a clear purpose statement followed by two critical notes (experimental status and latency). Both sentences earn their place by providing essential operational context without any fluff or repetition.

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

Completeness3/5

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

Given the tool's moderate complexity (external data fetch with latency), no annotations, and no output schema, the description is partially complete. It covers the core action and key constraints but lacks details on output format, success/failure indicators, and integration specifics. For an experimental tool with behavioral implications, more context would be beneficial.

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?

The tool has 0 parameters, and schema description coverage is 100% (empty schema). The description doesn't need to explain parameters, so it meets the baseline of 4. It appropriately focuses on the tool's action and behavioral context without redundant parameter details.

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 tool's purpose: 'Trigger a fetch of latest data from Plaid' with the verb 'trigger' and resource 'latest data from Plaid'. It distinguishes from siblings by focusing on external data synchronization rather than CRUD operations on local entities like assets or categories. However, it doesn't explicitly differentiate from potential similar fetch tools (none exist in siblings).

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

Usage Guidelines3/5

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

The description implies usage context through the note about fetch duration ('may take up to 5 minutes') and the '(Experimental)' label, suggesting caution. However, it doesn't provide explicit guidance on when to use this tool versus alternatives (e.g., manual updates or other sync methods), nor does it mention prerequisites like Plaid connectivity or authentication needs.

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