Skip to main content
Glama

Update recurring expense

crunch_update_recurring_expense
Idempotent

Update a recurring expense's schedule, line items, dates, or other fields; pause or resume it, and change only the values you pass without altering expenses already created.

Instructions

Change a recurring expense: its lines, its schedule (for example pause it with enabled=false, or change the next or end date), or any field via changes. Only what you pass changes. Expenses already created aren't affected.

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": {
      "recurring_expense_id": "<recurring_expense_id>"
    },
    "name": "crunch_update_recurring_expense"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNoNew internal note
changesNoRaw ExpenseDto fields to merge in, for example {"recurringEvent": {"recurringEventFrequency": "..."}} (advanced)
dry_runNoPreview: return the request that would be sent (for an update, the fields that would change) without sending it
enabledNoPause (false) or resume (true) the schedule
end_dateNoNew end date (YYYY-MM-DD)
line_itemsNoReplacement lines (all existing lines are replaced)
supplier_referenceNoNew supplier reference
next_occurrence_dateNoNew next date (YYYY-MM-DD)
recurring_expense_idYesRecurring expense ID (see crunch_list_recurring_expenses)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.7.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly=false, destructive=false and idempotent=true, so the bar is lower, yet the description adds real behavioral value: 'Only what you pass changes' discloses merge semantics, and 'Expenses already created aren't affected' discloses blast radius, which explains why destructive=false holds. It does not mention permission requirements or how the `changes` escape hatch bypasses validation.

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

Conciseness5/5

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

Three sentences, zero filler, with the scope statement front-loaded and the partial-update rule placed immediately after so the agent reads it before planning the call. Every sentence carries distinct information.

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

Completeness4/5

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

For a 9-parameter mutation tool with nested line-item objects and no output schema, the definition covers what changes, that unspecified fields are preserved, and the side-effect boundary on already-created expenses. What it omits — permissions, validation failures on the raw `changes` merge, and confirmation of return shape — is not fatal but leaves the agent guessing on error paths.

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

Parameters4/5

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

Schema coverage is 100%, so a 3 is the baseline, but the description earns more: it interprets `enabled` as pause/resume, frames `changes` as an advanced raw merge, and ties `next_occurrence_date`/`end_date`/`line_items` to the schedule-versus-lines distinction. It still leaves the interaction between explicit fields and `changes` (precedence, conflicts) unstated.

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?

States a specific verb and resource ('Change a recurring expense') and then enumerates the three axes of change: lines, schedule, or arbitrary fields via `changes`. That is well beyond tautology. It does not differentiate itself from the close sibling crunch_update_expense (non-recurring) or crunch_create_recurring_expense, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete usage examples embedded in the definition — pause with enabled=false, change next or end date — and states the partial-update rule ('Only what you pass changes'), which tells the agent not to resend the full object. It never names an alternative tool or an explicit when-not-to-use case, so it is clear context rather than full routing guidance.

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