Skip to main content
Glama

Advance a fixed cost now

recurring_advance

Advance a recurring expense template's next due date by one interval without booking a payment; requires the current cycle to be booked and uses expectedNextDueAt to prevent double advancement.

Instructions

Skip ahead one cycle: moves ONLY nextDueAt on by intervalMonths, without creating an expense. It only works once an expense was booked for the current due date, otherwise 409 recurring_expense_not_booked, and a paused template answers 400 recurring_paused. Any member may call it. To book the due payment use expense_create with recurringExpenseId and expectedRecurringNextDueAt instead: it creates the expense and advances the template in one step. To change the schedule itself use recurring_update. expectedNextDueAt is required and prevents double advancing: if the cycle was already advanced, 409 recurring_expense_already_advanced and nothing changes. Returns the updated template as recurringExpense.

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": {
      "id": "<id>",
      "expectedNextDueAt": "<expectedNextDueAt>"
    },
    "name": "recurring_advance"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesId of the fixed-cost template, as returned in recurringExpenses[].id by recurring_list or in recurringExpense.id by recurring_create.
wgCodeNoShare code of the flat (code from wg_list). Leave it out when the account belongs to one flat.
expectedNextDueAtYesnextDueAt of the template as you last read it from recurring_get or recurring_list (ISO 8601 with offset). Used as a concurrency guard.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.1
    • addedInput schema / properties / expectedNextDueAt / description
      Added value: +"nextDueAt of the template as you last read it from recurring_get or recurring_list (ISO 8601 with offset). Used as a concurrency guard."
    • addedInput schema / properties / id / description
      Added value: +"Id of the fixed-cost template, as returned in recurringExpenses[].id by recurring_list or in recurringExpense.id by recurring_create."
  2. First observedv0.1.0

TDQS

A4.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false and destructiveHint=false, and the description is consistent with them: it is a state mutation that leaves expenses untouched, and the expectedNextDueAt concurrency guard explains why it is not idempotent. It adds genuinely useful context beyond the annotations — permission scope ("Any member may call it") and specific failure codes (409 recurring_expense_not_booked, 400 recurring_paused, 409 recurring_expense_already_advanced). Note that only the concurrency-guard error guarantees no side effects; the description never states what a 409 not_booked leaves behind.

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?

Front-loaded with the core behavior and every clause carries information; nothing is filler. It is delivered as a single dense paragraph with chained colons, so the alternatives and error codes are harder to scan than they would be as discrete sentences.

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

Completeness5/5

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

There is no output schema, and the description closes the gap by stating it returns the updated template as recurringExpense. Combined with preconditions, error codes, permission scope and sibling routing, an agent has everything needed to call it correctly or pick a different tool.

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 the schema documents id, wgCode and expectedNextDueAt on its own. The description still adds the reason the guard exists ("prevents double advancing") and the read-then-pass protocol (value as last read from recurring_get/recurring_list), which the schema's "Used as a concurrency guard" only hints at.

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

Purpose5/5

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

"Skip ahead one cycle: moves ONLY nextDueAt on by intervalMonths, without creating an expense" states a specific verb (skip/advance), the exact resource and field mutated (nextDueAt), and explicitly negates the behavior an agent might otherwise assume (expense creation). That negation alone separates it from expense_create and recurring_update.

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

Usage Guidelines5/5

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

It names both alternatives with the condition that selects them: expense_create with recurringExpenseId/expectedRecurringNextDueAt to actually book the payment, recurring_update to change the schedule. Preconditions (an expense must already be booked for the current due date; paused templates reject) are stated up front, so the agent knows when this tool will fail.

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