Monarch Money MCP Server

Overview Schema Source Related Servers Discussions Admin

Get Account History

get_account_history

Read-only

Fetch account balance history within optional date bounds, using limit and offset to page through results. Follow next_offset until null to retrieve all matching snapshots.

Instructions

Get a page of balance history for account_id from get_accounts.

Optional YYYY-MM-DD bounds are inclusive; an omitted bound is unbounded. Filtering precedes local paging, preserving Monarch's snapshot order. limit: 1–1000 (default 100); offset: zero-based position after filtering. Follow next_offset until null. total_count counts all matching snapshots. Monarch still returns the full history upstream; the MCP response is bounded.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No
`offset`	No
`end_date`	No
`account_id`	Yes
`start_date`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`count`	Yes
`offset`	Yes
`history`	Yes
`account_id`	Yes
`next_offset`	Yes
`total_count`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedv0.5.0Sep 24, 2026

addedInput schema / properties / limit

Added value: +{
+  "default": 100,
+  "title": "Limit",
+  "type": "integer"
+}

addedInput schema / properties / offset

Added value: +{
+  "default": 0,
+  "title": "Offset",
+  "type": "integer"
+}

addedOutput schema / properties / count

Added value: +{
+  "title": "Count",
+  "type": "integer"
+}

addedOutput schema / properties / next_offset

Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "title": "Next Offset"
+}

addedOutput schema / properties / offset

Added value: +{
+  "title": "Offset",
+  "type": "integer"
+}

addedOutput schema / properties / total_count

Added value: +{
+  "title": "Total Count",
+  "type": "integer"
+}

changedOutput schema / required

Previous value: -[
-  "account_id",
-  "history"
-]New value: +[
+  "account_id",
+  "history",
+  "count",
+  "total_count",
+  "offset",
+  "next_offset"
+]

First observedv0.3.2May 30, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already mark the tool as read-only, and the description adds substantial behavioral detail: filtering precedes local paging, snapshot order is preserved, next_offset drives pagination, total_count counts matching snapshots, and the upstream response is always full while the MCP response is bounded. This is rich context beyond the annotations.

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 dense but well-structured and front-loaded with the core purpose. Every sentence adds semantic value around filtering, paging, or response bounds, with no filler or repeated schema information.

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?

The tool has an output schema, read-only annotations, and a description that covers parameters, pagination behavior, and response-bound implications. This is sufficient for an agent to invoke it correctly and interpret results, given the output schema.

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?

Schema description coverage is 0%, so the description must compensate, and it does. It defines YYYY-MM-DD bounds as inclusive and optional, limit range and default, offset as zero-based after filtering, and ties account_id to get_accounts.

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 states a specific verb and resource: 'Get a page of balance history for account_id from get_accounts.' This clearly distinguishes the tool from transaction-focused siblings like get_transactions and search_transactions.

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?

It provides clear operational context: date bounds, filtering before paging, pagination semantics, and a pointer that account_id comes from get_accounts. However, it does not explicitly state when to prefer this over alternatives or list exclusions.

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