Skip to main content
Glama
akutishevsky

LunchMoney MCP Server

get_budget_settings

Read-only

Retrieve budget period and display settings including granularity, period length, anchor date, and preferences for hiding no-activity, income, and rollover left to budget.

Instructions

Get budget period and display settings for the account (granularity, period length, anchor date, hide-no-activity preference, income option, rollover-left-to-budget setting).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The async handler function for get_budget_settings. It calls the Lunchmoney API GET /budgets/settings endpoint, handles errors, and returns the response data.
        async () => {
            try {
                const response = await api.get("/budgets/settings");
    
                if (!response.ok) {
                    return handleApiError(
                        response,
                        "Failed to get budget settings",
                    );
                }
    
                return dataResponse(await response.json());
            } catch (error) {
                return catchError(error, "Failed to get budget settings");
            }
        },
    );
  • The tool registration with description and readOnlyHint annotation. No input schema is defined since this tool takes no parameters.
    "get_budget_settings",
    {
        description:
            "Get budget period and display settings for the account (granularity, period length, anchor date, hide-no-activity preference, income option, rollover-left-to-budget setting).",
        annotations: {
            readOnlyHint: true,
        },
    },
  • Registration of the 'get_budget_settings' tool via server.registerTool() inside registerBudgetTools(). The tool is exported from src/index.ts on line 30.
    server.registerTool(
        "get_budget_settings",
        {
            description:
                "Get budget period and display settings for the account (granularity, period length, anchor date, hide-no-activity preference, income option, rollover-left-to-budget setting).",
            annotations: {
                readOnlyHint: true,
            },
        },
        async () => {
            try {
                const response = await api.get("/budgets/settings");
    
                if (!response.ok) {
                    return handleApiError(
                        response,
                        "Failed to get budget settings",
                    );
                }
    
                return dataResponse(await response.json());
            } catch (error) {
                return catchError(error, "Failed to get budget settings");
            }
        },
    );
  • The 'api' object with the 'get' method used by the handler to make the HTTP GET request.
    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),
    };
  • The BudgetSettings TypeScript interface defining the shape of the response from the /budgets/settings endpoint.
    export interface BudgetSettings {
        budget_period_granularity:
            | "day"
            | "week"
            | "month"
            | "year"
            | "twice a month";
        budget_period_quantity: number;
        budget_period_anchor_date: string;
        budget_hide_no_activity: boolean;
        budget_use_last_day_of_month: boolean;
        budget_income_option: "max" | "budgeted" | "activity";
        budget_rollover_left_to_budget: boolean;
    }
Behavior4/5

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

The description adds specific fields beyond the readOnlyHint annotation, which already indicates safe read. It clarifies exactly what settings are retrieved, but does not discuss limitations or side effects, which are minimal for a read-only, no-parameter tool.

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 sentence that efficiently lists the key settings. Every word adds value, and the structure is front-loaded with the verb 'get' and resource 'budget settings'.

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 fully informs the agent what will be retrieved. No additional context is needed for tool selection.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With zero parameters and 100% schema coverage, the description adds critical meaning by listing the returned settings. Without the description, the agent would have no idea what data is retrieved.

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 budget period and display settings for the account, listing specific fields like granularity and period length. It distinguishes from siblings like get_budget_summary by specifying the exact settings returned.

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 budget settings are needed but does not provide explicit guidance on when to use this vs alternatives like upsert_budget or get_budget_summary. No exclusions or prerequisites are mentioned.

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