monarch-mcp2

Reports Create Saved Report

reports_create_saved_report

Create a saved report in Monarch Money by applying transaction filters, grouping options, and a timeframe to analyze financial data.

Instructions

Create saved report. This may create or update Monarch data.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

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

Input Schema

Name	Required	Description	Default
`name`	Yes
`fields`	No	Optional dotted output field paths to return, such as ['id', 'merchant.name', 'category.name'].
`filters`	No
`group_by`	No		category
`timeframe`	No
`output_mode`	No	Output shape to return. Use summary for compact CLI-style defaults, full for complete structured data without raw, and raw for complete structured data including raw payloads.	summary
`session_path`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 5, 2026

TDQS

C2.4/5.0

Behavior2/5

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

Annotations indicate readOnlyHint=false, so it's a write operation. The description adds 'may create or update' which is ambiguous—does it create a new report or update an existing one? No further disclosure of side effects, permissions, or behavior is given.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very short (two sentences), which is concise, but it lacks necessary information. It is not verbose, but its brevity leads to incompleteness.

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?

The tool has 7 parameters including a complex nested object (filters) and no output schema. The description does not explain what the tool returns, how filters work, or the effect of output_mode. This is insufficient for correct invocation.

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

Parameters2/5

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

Schema description coverage is only 29% (2 of 7 parameters have descriptions). The tool description does not explain any parameter's meaning or usage. The schema itself provides minimal descriptions; the description adds no value.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states 'Create saved report' which is a specific verb+resource, but it does not distinguish from the sibling tool 'reports_update_saved_report'. The added phrase 'This may create or update Monarch data' is ambiguous, blurring the purpose.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus alternatives like reports_update_saved_report or reports_get_saved_report. The description does not mention context, prerequisites, or exclusions.

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

Deploy Server