Monarch Money MCP Server

Overview Schema Source Related Servers Discussions Admin

Complete Financial Overview

get_complete_financial_overview

Read-only

Fetch a compact financial overview covering account balances, budget totals, cashflow, and transaction summaries for a specified period.

Instructions

Fetch a compact financial overview; verbose=True includes full API details.

period is a start date or phrase such as 'this month', 'last month', or 'this year'; the end is always today. 'last month' therefore includes the current month too. Transactions and their summary use one page of up to 500 entries, not the full history. Failed API sections contain errors while successful sections remain. Default: account IDs/names/balances/types, monthly budget totals, cashflow totals, and a transaction summary. Raw transactions/categories are null unless verbose. Use their dedicated tools for details. batch_metadata.transactions_truncated is true if more transactions exist, false for a complete page, null if unknown.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`period`	No		this month
`verbose`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`period`	Yes
`budgets`	No
`verbose`	No
`accounts`	No
`cashflow`	No
`categories`	No
`transactions`	No
`batch_metadata`	No
`transaction_summary`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.5.0Sep 24, 2026

addedInput schema / properties / verbose

Added value: +{
+  "default": false,
+  "title": "Verbose",
+  "type": "boolean"
+}

addedOutput schema / properties / verbose

Added value: +{
+  "default": false,
+  "title": "Verbose",
+  "type": "boolean"
+}

First observedv0.3.2May 30, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Beyond the readOnlyHint annotation, the description discloses significant behavioral details: the single-page 500-entry limit, the failure behavior ('Failed API sections contain errors while successful sections remain'), the null default for raw transactions/categories unless verbose, and the transactions_truncated metadata flag. These go well beyond what annotations convey, offering the agent a clear model of the tool's output boundaries and error handling.

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?

The description is dense but not bloated; every sentence adds value. It opens with the main purpose, then systematically covers period semantics, transaction limits, failure behavior, defaults, and the truncation flag. A minor redundancy exists between the 500-entry limit and the truncation flag explanation, but overall it remains efficient and well-structured.

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's complexity (overview with many fields) and the presence of an output schema, the description covers all essential invocation details: parameter syntax, default/verbose returns, transaction pagination behavior, error handling, and a signal for incomplete data (transactions_truncated). An agent can call this tool correctly without needing additional information.

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 has zero description coverage for its parameters, so the description carries the full burden. It thoroughly explains 'period' with concrete examples ('this month', 'last month', 'this year') and the 'always today' end date, and defines 'verbose' as including full API details. This fully compensates for the schema's lack of parameter descriptions.

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 'Fetches a compact financial overview' and enumerates the specific components (account IDs/names/balances/types, monthly budget totals, cashflow totals, transaction summary). It differentiates itself from sibling tools by explicitly mentioning 'Use their dedicated tools for details', making it unmistakable that this is an aggregate overview rather than a detailed data tool.

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 provides explicit guidance on when to use this tool versus alternatives: it says to use dedicated tools for detailed transactions/categories, and it highlights the 500-entry page limit, implying that full history requires the dedicated transaction tool. It also clarifies the period parameter's semantics (start date or phrases, end always today) and the verbose flag's effect, giving the agent complete context for invocation.

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