Skip to main content
Glama
akutishevsky

LunchMoney MCP Server

by akutishevsky
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

upsert_budget

Idempotent

Create or update a budget for a category and period. Set amounts to control spending and track financial goals.

Instructions

Create or update a budget for a category and budget period. The start_date must be a valid budget period start for the account (see get_budget_settings).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
notesNoOptional notes for the budget period.
amountYesBudget amount.
currencyNoThree-letter lowercase currency code (defaults to primary currency).
start_dateYesBudget period start date in YYYY-MM-DD format. Must be a valid budget period start; if not, the API returns the previous and next valid start dates.
category_idYesCategory ID for the budget.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.3
  2. Removedv1.0.2
  3. Changed9 schema fields changedv1.0.1
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / amount
      Added value: +{
+  "description": "Budget amount.",
+  "type": "number"
+}
    • addedInput schema / properties / category_id
      Added value: +{
+  "description": "Category ID for the budget.",
+  "type": "number"
+}
    • addedInput schema / properties / currency
      Added value: +{
+  "description": "Three-letter lowercase currency code (defaults to primary currency).",
+  "maxLength": 3,
+  "minLength": 3,
+  "type": "string"
+}
    • removedInput schema / properties / input
      Removed value: -{
-  "additionalProperties": false,
-  "properties": {
-    "amount": {
-      "description": "Budget amount",
-      "type": "number"
-    },
-    "category_id": {
-      "description": "Category ID for the budget",
-      "type": "number"
-    },
-    "currency": {
-      "description": "Currency for budget (defaults to primary currency)",
-      "type": "string"
-    },
-    "start_date": {
-      "description": "Budget month start date in YYYY-MM-DD format",
-      "type": "string"
-    }
-  },
-  "required": [
-    "start_date",
-    "category_id",
-    "amount"
-  ],
-  "type": "object"
-}
    • addedInput schema / properties / notes
      Added value: +{
+  "description": "Optional notes for the budget period.",
+  "maxLength": 350,
+  "type": "string"
+}
    • addedInput schema / properties / start_date
      Added value: +{
+  "description": "Budget period start date in YYYY-MM-DD format. Must be a valid budget period start; if not, the API returns the previous and next valid start dates.",
+  "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "input"
-]New value: +[
+  "start_date",
+  "category_id",
+  "amount"
+]
  4. First observedv1.0.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already indicate idempotentHint=true. The description adds useful behavior about start_date validation and error response returning alternative dates, which is beyond 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 two concise sentences. The first states the purpose, the second gives a key constraint. No unnecessary words.

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?

The description explains the date validation but does not mention what the response contains (e.g., the budget object) or how updates work (e.g., combining category_id and start_date). For a tool with no output schema, this leaves gaps.

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?

Schema description coverage is 100%, so baseline is 3. The description adds the hint to see get_budget_settings for start_date, providing marginal extra value but not significantly enhancing understanding.

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 'Create or update a budget for a category and budget period', specifying the verb and resource. This distinguishes it from sibling tools like 'remove_budget' and 'get_budget_settings'.

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

Usage Guidelines4/5

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

The description advises that start_date must be a valid budget period start and refers to get_budget_settings for finding valid dates. This provides context for when to use the tool, though it lacks explicit exclusions or alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools