monarch-mcp2

Budget Reset Budget Rollover

budget_reset_budget_rollover

Destructive

Reset the rollover amount for a specified budget, clearing any carried-over balance.

Instructions

Reset budget rollover. This may delete, clear, reset, or otherwise remove 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": {
      "month": "<month>"
    },
    "name": "budget_reset_budget_rollover"
  }
}

Input Schema

Name	Required	Description	Default
`month`	Yes
`fields`	No	Optional dotted output field paths to return, such as ['id', 'merchant.name', 'category.name'].
`category_id`	No
`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
`session_path`	No
`starting_balance`	No
`category_group_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 5, 2026

TDQS

C2.4/5.0

Behavior2/5

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

Annotations already indicate destructiveHint=true, and the description echoes this with 'may delete, clear, reset, or otherwise remove data'. However, it lacks specificity about what exactly is removed, which rollovers are affected, and whether parameters like category_id scope the action.

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

Conciseness3/5

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

The description is brief (two short sentences), but the second sentence is redundant and vague. It is front-loaded but could be more informative without increasing length.

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?

Given 7 parameters, no output schema, and destructive nature, the description fails to provide sufficient context. It does not explain how parameters interact, what returns are expected, or how this differs from sibling tools.

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?

The description adds no value to the input schema. With only 29% schema description coverage, the required parameter 'month' and key parameters like 'category_id' have no explanation in the description. The tool's core behavior is left vague.

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 states 'Reset budget rollover', clearly indicating the action and resource. It differentiates from siblings like 'budget_reset_budget' which resets the entire budget, but does not elaborate on what exactly 'reset' means, leaving some ambiguity.

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 explicit guidance on when to use this tool versus alternatives like 'budget_set_budget_rollover' or 'budget_reset_budget'. The description implies use for resetting rollovers but does not provide usage context or exclusions.

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

Deploy Server