monarch-mcp2

Budget Set Budget Category Rollover

budget_set_budget_category_rollover

Configure budget category rollover to carry over unused funds to future months. Set enabled, frequency, and target amount for a Monarch Money category.

Instructions

Set budget category rollover. This may create or update Monarch data.

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": {
      "category_id": "<category_id>",
      "enabled": "<enabled>"
    },
    "name": "budget_set_budget_category_rollover"
  }
}

Input Schema

Name	Required	Description	Default
`fields`	No	Optional dotted output field paths to return, such as ['id', 'merchant.name', 'category.name'].
`enabled`	Yes
`frequency`	No
`category_id`	Yes
`output_mode`	No	Output shape to return. Use summary for compact CLI-style defaults, full for complete structured data without raw, and raw for complete structured data including raw payloads.	summary
`start_month`	No
`session_path`	No
`rollover_type`	No
`target_amount`	No
`apply_to_future`	No
`starting_balance`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 5, 2026

TDQS

C2.4/5.0

Behavior3/5

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

Annotations already indicate it's not read-only (readOnlyHint=false) and not destructive (destructiveHint=false). The description adds that it 'may create or update Monarch data,' which confirms the mutation behavior. This adds some value beyond annotations but doesn't disclose specific side effects or authorization needs.

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

Conciseness2/5

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

The description is a single vague sentence. While concise, it lacks important details and is not well-structured (no bullet points, no parameter breakdown).

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

Completeness1/5

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

Given the high parameter count (11), no output schema, and minimal description, the tool definition is severely incomplete. It does not explain what rollover does, how parameters interact, or what the result looks like.

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

Parameters1/5

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

With 11 parameters and only 18% schema description coverage, the description provides no explanation of any parameters. It fails to add meaning beyond the input schema, leaving the agent to infer parameter semantics from names alone.

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?

The description clearly states that the tool sets budget category rollover and may create or update data. It distinguishes itself from sibling tools like budget_set_budget_group_rollover by focusing on category-level rollover, but it doesn't define 'rollover' itself.

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?

There is no guidance on when to use this tool versus alternatives (e.g., budget_reset_budget_rollover, budget_set_budget_group_rollover). No context about prerequisites or typical use cases is provided.

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

Deploy Server