monarchmoney-node

get_cashflow

Retrieve cashflow data grouped by category, category group, and merchant for analysis of income and expenses over a specified date range.

Instructions

Get cashflow data grouped by category, category group, and merchant. 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_cashflow"
  }
}

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

A3.9/5.0

Behavior3/5

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

With no annotations provided, the description carries the full burden. It mentions the data is grouped and defaults to the current month, which adds useful context. However, it does not disclose whether the operation is read-only, whether there are any side effects, limits, or how errors are handled. For a non-annotated tool, this is moderately transparent.

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 extremely concise, consisting of two short sentences that front-load the key action and grouping details. Every word provides value, and there is no redundancy.

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?

Given the presence of several sibling tools and no output schema, the description adequately covers the input and default behavior. However, it does not describe the structure of the returned data (e.g., fields available at each grouping level). For a data retrieval tool, this omission reduces completeness.

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

Parameters4/5

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

The input schema has 100% description coverage, but the description adds significant value by stating that the tool defaults to the current month when parameters are omitted. This clarifies the behavior beyond the schema definitions, which only specify the format.

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 verb 'Get', the resource 'cashflow data', and specifies it is grouped by category, category group, and merchant. This level of detail distinguishes it from sibling tools like 'get_cashflow_summary' which likely provides a summary, and 'get_transactions' which returns raw data. The default to current month adds clarity.

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 implies usage for obtaining grouped cashflow data but lacks explicit guidance on when to use this tool versus alternatives such as 'get_cashflow_summary', 'get_transactions', or other related tools. No when-not-to-use conditions or alternative recommendations are provided.

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