Skip to main content
Glama
akutishevsky

LunchMoney MCP Server

get_all_manual_accounts

Read-only

Retrieve a list of all manually-managed accounts, including assets, to track non-synced financial data and balances.

Instructions

Get a list of all manually-managed accounts associated with the user. (Formerly known as assets in the v1 API.)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The async handler function for get_all_manual_accounts. It calls GET /manual_accounts via the api helper and returns the JSON response.
    async () => {
        try {
            const response = await api.get("/manual_accounts");
    
            if (!response.ok) {
                return handleApiError(
                    response,
                    "Failed to get manual accounts",
                );
            }
    
            return dataResponse(await response.json());
        } catch (error) {
            return catchError(error, "Failed to get manual accounts");
        }
    },
  • The registerManualAccountTools function registers 'get_all_manual_accounts' (and other manual account tools) on the McpServer via server.registerTool().
    export function registerManualAccountTools(server: McpServer) {
        server.registerTool(
            "get_all_manual_accounts",
            {
                description:
                    "Get a list of all manually-managed accounts associated with the user. (Formerly known as `assets` in the v1 API.)",
                annotations: {
                    readOnlyHint: true,
                },
            },
            async () => {
                try {
                    const response = await api.get("/manual_accounts");
    
                    if (!response.ok) {
                        return handleApiError(
                            response,
                            "Failed to get manual accounts",
                        );
                    }
    
                    return dataResponse(await response.json());
                } catch (error) {
                    return catchError(error, "Failed to get manual accounts");
                }
            },
        );
  • Input schema for get_all_manual_accounts — no input parameters are defined (empty schema), with annotations readOnlyHint: true.
    {
        description:
            "Get a list of all manually-managed accounts associated with the user. (Formerly known as `assets` in the v1 API.)",
        annotations: {
            readOnlyHint: true,
        },
    },
  • src/index.ts:31-33 (registration)
    The top-level call that registers the manual account tools on the MCP server.
    registerManualAccountTools(server);
    registerPlaidAccountTools(server);
    registerCryptoTools(server);
  • The api.get() helper used by the handler to make the HTTP GET request to /manual_accounts.
    export const api = {
        get: (path: string) => apiRequest("GET", path),
        post: (path: string, body?: unknown) => apiRequest("POST", path, body),
        put: (path: string, body: unknown) => apiRequest("PUT", path, body),
        delete: (path: string, body?: unknown) => apiRequest("DELETE", path, body),
        upload: (path: string, formData: FormData) =>
            apiUpload("POST", path, formData),
    };
Behavior3/5

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

Annotations already provide 'readOnlyHint: true'. The description repeats this intent with 'Get a list' but adds no further behavioral details (e.g., sorting, pagination, data format). The historical note is not behavioral.

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 that immediately states the action and scope. No extraneous words. Perfectly front-loaded.

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

Completeness5/5

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

Given no parameters and no output schema, the description sufficiently explains what the tool does and what it returns (a list of accounts). No gaps identified.

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?

There are zero parameters. The description adds no parameter information, but per guidelines, 0 parameters yields a baseline of 4. No additional semantic value needed.

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 tool retrieves a list of manually-managed accounts for the user. It distinguishes from siblings like 'get_all_plaid_accounts' (different account type) and 'get_single_manual_account' (singular). The mention of the former v1 API name adds historical clarity.

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 use when needing all manual accounts but offers no explicit guidance on when not to use or comparisons with alternatives like 'get_single_manual_account' or 'get_all_plaid_accounts'. Context from sibling names is not leveraged.

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