Monarch Money MCP Server

Overview Schema Source Related Servers Discussions Admin

Get Recurring Transactions

get_recurring_transactions

Read-only

See scheduled recurring transactions for any date range, including amounts, accounts, and merchant details. It shows upcoming scheduled occurrences, not posted transaction history.

Instructions

Get scheduled recurring occurrences, not the posted transaction history.

Dates accept ISO dates or natural language such as "today" or "last month". With neither date, fetch the current calendar month. With only one date, use the beginning or end of that date's month for the missing bound.

The recurring.recurringTransactionItems list includes each occurrence's date, amount, account, category, transactionId (when matched), and stream containing the merchant ID, frequency, and expected amount. isPast describes the date, not whether a bill was paid. Use get_transactions(is_recurring=True) for recorded transactions instead.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`end_date`	No
`start_date`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`recurring`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.5.0Sep 24, 2026

addedInput schema / properties / end_date

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "End Date"
+}

addedInput schema / properties / start_date

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Start Date"
+}

First observedv0.3.2May 30, 2026

TDQS

A5/5.0

Behavior5/5

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

Beyond the readOnlyHint and openWorldHint annotations, the description adds valuable behavioral context: it defines the recurring.recurringTransactionItems return structure, clarifies that isPast refers to the occurrence date rather than payment status, and explains the default date-range behavior. This goes well beyond what annotations or schema alone provide.

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?

The description is front-loaded with the core purpose, followed by concise, logically grouped date semantics and return-structure details. Every sentence carries useful information with no repetition or filler. It is appropriately sized for the tool's complexity.

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?

Given the tool has only two optional parameters, an output schema, and read-only annotations, the description covers everything needed for correct invocation and interpretation: what is returned, how dates behave, and how isPast should be understood. It is complete without being bloated.

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

Parameters5/5

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

The input schema provides no descriptions and 0% coverage, but the description fully compensates. It explains that dates accept ISO or natural language, defines the default month when neither date is provided, and specifies how a missing bound is derived from the single provided date. This adds substantial meaning beyond the bare schema.

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?

The description opens with a specific verb and resource: 'Get scheduled recurring occurrences, not the posted transaction history.' This immediately distinguishes it from transaction-history tools, and the final sentence names get_transactions(is_recurring=True) as the recorded-transaction alternative. The purpose is unambiguous and clearly differentiated from siblings.

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?

The description explicitly tells the agent when to use this tool: when scheduled recurring occurrences are needed, not posted history. It also names the exact alternative, get_transactions(is_recurring=True), with the condition that selects it. Date-bound defaults are documented precisely, leaving no guesswork about invocation.

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