Skip to main content
Glama
Sign In
monarch-mcp2-obot

monarch-mcp2-obot

by dcode
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Budget Reset Budget Rollover

budget_reset_budget_rollover
Destructive

Reset the rollover balance for a budget month, optionally for specific categories or groups, to clear prior carryover and start fresh.

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

NameRequiredDescriptionDefault
monthYes
fieldsNoOptional dotted output field paths to return, such as ['id', 'merchant.name', 'category.name'].
category_idNo
output_modeNoOutput 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
starting_balanceNo
category_group_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.3/5.0
Behavior2/5

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

The description says it 'may delete, clear, reset, or otherwise remove data,' which is a warning, but this mostly restates the destructiveHint=true annotation. It doesn't say what rollover data is affected, whether the operation is reversible, or how month/category scoping changes the blast radius. No contradiction with annotations, but no meaningful new behavioral disclosure.

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 short and front-loaded with the main action, but the second sentence ('This may delete, clear, reset...') is generic and largely duplicates the destructiveHint annotation. It is appropriately concise in length, but the second sentence doesn't earn its place with specific information.

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?

For a destructive tool with six parameters and no output schema, this provides almost no operational context. It doesn't define what rollover data is reset, what the month parameter selects, what starting_balance means, whether the action covers specific categories/groups, or what the response contains. This is inadequate for safe invocation.

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

Parameters2/5

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

The tool description explains none of the six parameters. Schema coverage is only 33% (fields and output_mode), and critical parameters like month, category_id, category_group_id, and starting_balance remain unexplained. The description doesn't compensate for the low coverage, leaving the agent without enough information to set parameters correctly.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the action and resource ('Reset budget rollover'), but it adds little beyond the tool title and gives no details about scope (category, group, or whole budget). It also doesn't distinguish this from closely related siblings like budget_reset_budget, budget_clear_budget, or budget_set_budget_category_rollover. The generic warning about deleting data doesn't clarify the purpose.

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, what prerequisites or context are needed, or what alternatives exist. An agent cannot tell from the description whether to choose this over budget_set_budget_category_rollover or budget_reset_budget. The name hints at the intended use, but the description provides no decision support.

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