Skip to main content
Glama
YNAB MCP Server

YNAB MCP Server

by rgarcia

Updatemonthcategory

updateMonthCategory

Set or change the assigned (budgeted) amount for a category in a specific month of a YNAB plan, enabling monthly budget adjustments.

Instructions

Update a category for a specific month. Only budgeted (assigned) amount can be updated.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "plan_id": "<plan_id>",
      "month": "<month>",
      "category_id": "<category_id>",
      "category": "<category>"
    },
    "name": "updateMonthCategory"
  }
}

Input Schema

NameRequiredDescriptionDefault
monthYesThe plan month in ISO format (e.g. 2016-12-01) ("current" can also be used to specify the current calendar month (UTC))
plan_idYesThe id of the plan. "last-used" can be used to specify the last used plan and "default" can be used if default plan selection is enabled (see: https://api.ynab.com/#oauth-default-plan).
categoryYes
category_idYesThe id of the category

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It confirms a mutation and constrains the writable field, but says nothing about authorization requirements, whether other category fields are preserved, or reversibility of the month assignment.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, front-loaded with the operation and immediately qualified by the field constraint. Nothing is wasted; the gap is under-specification rather than verbosity.

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

Completeness2/5

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

A mutation tool with four required parameters, a nested object, no annotations, and no output schema. The description should address permissions/scope and what a successful update returns, but it stops at the field constraint.

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 coverage is 75%, and the description adds meaning by clarifying that only the nested 'budgeted' field is mutable. It does not explain the milliunits convention or ambiguity around month values, which the schema already documents.

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?

States a specific verb and resource: update a category's budgeted amount for a specific month. The month scoping distinguishes it in spirit from a general category update sibling, though it never names that sibling explicitly.

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

Usage Guidelines2/5

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

No when-to-use guidance and no reference to alternatives such as updateCategory or getMonthCategoryById. The only constraint given ('Only budgeted can be updated') limits what can be changed rather than routing the agent among tools.

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