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

monarch-mcp2-obot

by dcode
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Budget Set Budget Group Amount

budget_set_budget_group_amount

Set or update a budget amount for a specific category group and month in Monarch Money, creating or adjusting budget data as needed.

Instructions

Set budget group amount. 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": {
      "month": "<month>",
      "category_group_id": "<category_group_id>",
      "amount": "<amount>"
    },
    "name": "budget_set_budget_group_amount"
  }
}

Input Schema

NameRequiredDescriptionDefault
monthYes
amountYes
fieldsNoOptional dotted output field paths to return, such as ['id', 'merchant.name', 'category.name'].
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
default_amountNo
apply_to_futureNo
category_group_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

The phrase 'This may create or update Monarch data' aligns with annotations showing readOnlyHint=false and idempotentHint=false, but adds little beyond what those annotations already imply. It does not disclose side effects of parameters like default_amount or apply_to_future, nor any rollover or reset behavior, though the mutation warning prevents contradiction.

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 extremely short — two sentences, no filler, and the operation is stated at the front. However, the brevity veers into under-specification rather than disciplined conciseness, so it doesn't earn a 5.

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?

With 7 parameters, 3 required, low schema coverage, no output schema, and a large family of closely related budget tools, the description is too thin for an agent to invoke it confidently. It omits month format, behavior of default_amount/apply_to_future, return shape, and any guidance on how 'group amount' interacts with category-level budgets.

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?

Schema description coverage is only 29%, and the description does not compensate. It provides no explanation for required parameters like month format, amount units, or category_group_id semantics, and no context for optional parameters like default_amount or apply_to_future. The description adds essentially no parameter-level meaning beyond the schema's sparse field names.

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 the operation: 'Set budget group amount' — a specific verb and resource. It distinguishes from sibling tools like budget_set_budget_amount and budget_set_flex_budget_amount through the 'group' qualifier, though it doesn't explain what a budget group amount is or how it differs semantically.

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 the many related budget mutation tools (e.g., budget_set_budget_amount, budget_set_budget_group_rollover, budget_set_flex_budget_amount). The only hint is the tool name and the generic 'may create or update' note, leaving the agent to infer selection criteria.

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