monarchmoney-node

get_recurring_transactions

Retrieve upcoming recurring transactions such as subscriptions and bills for a selected date range or default to the current month.

Instructions

Get upcoming recurring transactions (subscriptions, bills). Defaults to current month.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_recurring_transactions"
  }
}

Input Schema

Name	Required	Description	Default
`start_date`	No	Start date in YYYY-MM-DD format
`end_date`	No	End date in YYYY-MM-DD format

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.1May 28, 2026

TDQS

B3.4/5.0

Behavior2/5

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

With no annotations, the description carries the burden of disclosing behavioral traits. It only notes default behavior (current month) but does not mention whether it is read-only, pagination limits, or other side effects. The update description is minimal.

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 a single sentence that immediately conveys the tool's purpose and default behavior. No extraneous words or redundant information. It is optimally concise and front-loaded.

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?

Given the lack of an output schema, the description should hint at what the response contains (e.g., list of transactions). It does not. Additionally, it does not differentiate from similar sibling tools like 'get_subscription_details'. The description is too minimal to be fully contextually complete.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents both parameters (start_date, end_date) with format hints. The description adds no additional parameter meaning beyond stating the default timeframe. Baseline score of 3 is appropriate.

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 clearly states the tool retrieves upcoming recurring transactions (subscriptions, bills). The verb 'get' and resource 'recurring transactions' are explicit, and it distinguishes from siblings like 'get_transactions' by specifying 'upcoming recurring'.

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

Usage Guidelines3/5

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

The description mentions defaulting to the current month, which implies when no dates are provided, but it does not explicitly state when to use this tool over alternatives like 'get_subscription_details' or 'get_transactions'. No when-not-to-use guidance is given.

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