monarchmoney-node

get_aggregate_snapshots

Retrieve daily aggregate net worth across all accounts for a date range, with optional account type filter to track financial trends.

Instructions

Get daily aggregate net worth across all accounts over time.

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_aggregate_snapshots"
  }
}

Input Schema

Name	Required	Description
`start_date`	No	Start date in YYYY-MM-DD format
`end_date`	No	End date in YYYY-MM-DD format
`account_type`	No	Filter by account type

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.1May 28, 2026

TDQS

A3.7/5.0

Behavior3/5

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

No annotations provided. Description discloses that it returns daily aggregates across all accounts, but lacks information on data freshness, performance implications, or whether date range is required.

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?

Single sentence of 8 words, front-loaded with key action and resource. No redundant information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Description covers basic function but omissions: no mention of return format, default date behavior, or relationship to similar tools. With no output schema, more detail on response is warranted.

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 coverage is 100% with parameter descriptions. Description does not add additional meaning beyond what the schema already provides for start_date, end_date, and account_type.

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?

Description clearly states the verb 'Get', the resource 'daily aggregate net worth', and scope 'across all accounts over time'. It distinguishes from sibling tools like get_accounts or get_cashflow.

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?

Description implies usage for overall net worth trends but does not explicitly state when to use this tool vs alternatives like get_cashflow or get_account_history. No when-not guidance.

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