monarch-mcp2

Budget Set Budget Group Variability

budget_set_budget_group_variability

Set the variability (fixed, flexible, or non-monthly) for a budget group in Monarch to control spending patterns and forecast accuracy.

Instructions

Set budget group variability. 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_group_id": "<category_group_id>",
      "variability": "<variability>"
    },
    "name": "budget_set_budget_group_variability"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 5, 2026

TDQS

C2.7/5.0

Behavior2/5

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

Annotations already indicate readOnlyHint=false and destructiveHint=false. The description adds 'This may create or update Monarch data,' which is vague and doesn't specify what gets created/updated, permissions needed, or side effects. Minimal added value beyond annotations.

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?

The description is a single sentence, very concise. It could be front-loaded with more critical information, but it avoids verbosity. Every word earns its place, though more structure would be beneficial.

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 the tool has 5 parameters, no output schema, and moderate annotations, the description is too brief. It lacks context about return values, behavior on different inputs, and how it fits into the broader budgeting workflow.

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?

With 40% schema description coverage and 5 parameters, the description adds no meaning beyond the schema. It does not explain the variability enum values or the purpose of required parameters like category_group_id, leaving the agent without clarity.

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 'Set budget group variability' with a specific verb and resource. It clearly indicates the action, but does not explicitly differentiate from sibling tools like budget_set_budget_category_variability, relying on the name for disambiguation.

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 guidance is provided on when to use this tool versus alternatives such as budget_set_budget_group_amount or budget_set_budget_group_rollover. There is no mention of prerequisites or conditions for use.

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

Deploy Server