Monexa

Update recurring expense

update_recurring_expense

DestructiveIdempotent

Changes a recurring expense; only the fields you pass change. Set isActive to false to pause it and to true to resume it; resuming continues from the next due day without adding records for the days missed while paused. Set clearEndDate to true to make it repeat indefinitely. Records it already added are not changed.

Input Schema

Name	Required	Description
`id`	Yes	Recurring expense ID from list_recurring_expenses.
`amount`	No	New amount of each occurrence, at least 0.01.
`endDate`	No	New last day a record may be added. Format: YYYY-MM-DD or an RFC 3339 timestamp such as 2026-03-05T14:30:00Z.
`currency`	No	New currency of the amount.
`isActive`	No	false pauses the recurring expense, true resumes it.
`frequency`	No	New frequency.
`startDate`	No	New first due day; today or later. Format: YYYY-MM-DD or an RFC 3339 timestamp such as 2026-03-05T14:30:00Z.
`categoryId`	No	New category ID from list_categories.
`description`	No	New description; an empty string removes it.
`clearEndDate`	No	true removes the end date.
`paymentMethodId`	No	New payment method ID from list_payment_methods.

Output Schema

Name	Required	Description	Default
`recurringExpense`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 1, 2026

changedInput schema / properties / currency / enum

Previous value: -[
-  "MKD",
-  "EUR",
-  "USD",
-  "AUD",
-  "CHF",
-  "GBP"
-]New value: +[
+  "MKD",
+  "EUR",
+  "USD",
+  "AUD",
+  "CHF",
+  "GBP",
+  "HUF",
+  "RSD"
+]

changedOutput schema / properties / recurringExpense / properties / currency / enum

Previous value: -[
-  "MKD",
-  "EUR",
-  "USD",
-  "AUD",
-  "CHF",
-  "GBP"
-]New value: +[
+  "MKD",
+  "EUR",
+  "USD",
+  "AUD",
+  "CHF",
+  "GBP",
+  "HUF",
+  "RSD"
+]

First observedOct 18, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true; the description goes further by stating that resume continues from the next due day without backfilling missed occurrences, that clearEndDate makes it repeat indefinitely, and that already-added records are untouched. That is real behavioral context beyond the structured flags.

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?

Four short sentences, front-loaded with the partial-update contract before per-parameter guidance. Slight repetition in the repeated "Set X to..." construction, but no filler.

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?

With 11 parameters, full schema coverage and an output schema, the description covers the non-obvious behaviors an agent could get wrong (pause/resume, backfill, clearEndDate). Only the relationship to the delete/create siblings is missing.

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 baseline is 3, but the description adds semantics the schema lacks: what isActive=false/true actually do over time, and that clearEndDate produces indefinite repetition rather than merely removing a field.

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?

Opens with a specific verb+resource ("Changes a recurring expense") and immediately scopes it as a partial update ("only the fields you pass change"). It doesn't explicitly distinguish itself from create_recurring_expense or delete_recurring_expense, but the intent is unambiguous.

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 clear operational context: pass only the fields to change, use isActive=false to pause and true to resume. It never names the sibling delete_recurring_expense as the alternative for removal or create for new ones, so the when-not case is left implicit.

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

All Monexa tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.