Skip to main content
Glama
akutishevsky

LunchMoney MCP Server

get_single_plaid_account

Read-only

Retrieve detailed information for a specific Plaid-synced account using its ID. Requires prior discovery of account IDs via the list accounts tool.

Instructions

Get details of a single Plaid (synced) account by ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
accountIdYesId of the Plaid account to query. Call get_all_plaid_accounts first to discover ids.

Implementation Reference

  • Registration of the 'get_single_plaid_account' tool with its schema and handler logic. The handler accepts an 'accountId' parameter, calls GET /plaid_accounts/{accountId}, and returns the response.
    server.registerTool(
        "get_single_plaid_account",
        {
            description:
                "Get details of a single Plaid (synced) account by ID.",
            inputSchema: {
                accountId: z.coerce
                    .number()
                    .describe(
                        "Id of the Plaid account to query. Call get_all_plaid_accounts first to discover ids.",
                    ),
            },
            annotations: {
                readOnlyHint: true,
            },
        },
        async ({ accountId }) => {
            try {
                const response = await api.get(`/plaid_accounts/${accountId}`);
    
                if (!response.ok) {
                    return handleApiError(
                        response,
                        "Failed to get Plaid account",
                    );
                }
    
                return dataResponse(await response.json());
            } catch (error) {
                return catchError(error, "Failed to get Plaid account");
            }
        },
    );
  • The handler function that executes the tool logic: takes accountId, makes a GET request to /plaid_accounts/{accountId}, and returns the account data.
    async ({ accountId }) => {
        try {
            const response = await api.get(`/plaid_accounts/${accountId}`);
    
            if (!response.ok) {
                return handleApiError(
                    response,
                    "Failed to get Plaid account",
                );
            }
    
            return dataResponse(await response.json());
        } catch (error) {
            return catchError(error, "Failed to get Plaid account");
        }
    },
  • Input schema defining the 'accountId' parameter as a coerced number.
    inputSchema: {
        accountId: z.coerce
            .number()
            .describe(
                "Id of the Plaid account to query. Call get_all_plaid_accounts first to discover ids.",
            ),
    },
Behavior4/5

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

Annotations already declare readOnlyHint=true, confirming a safe read operation. The description adds context by specifying 'Plaid (synced) account', which distinguishes it from manual accounts. No contradictions, and the description aligns with the annotation.

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, concise sentence with no unnecessary words. It is front-loaded with the core action and resource, making it easy to parse.

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 simplicity of the tool (one required parameter, read-only, no output schema), the description is largely sufficient. It allows an agent to understand the basic operation, though details about return value format are omitted but implicitly understood from the verb 'get details'.

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 schema has 100% coverage with a descriptive parameter comment. The tool description adds no extra parameter information beyond what the schema already provides. According to guidelines, baseline is 3 for high coverage, and no additional value is provided.

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 details' and the resource 'single Plaid (synced) account by ID', which precisely communicates the tool's function. It is distinct from sibling tools like get_all_plaid_accounts or get_single_manual_account.

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 does not explicitly state when to use this tool vs alternatives. However, the parameter description advises to call get_all_plaid_accounts first to discover IDs, which indirectly guides usage. The main description lacks explicit guidance, making it merely adequate.

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