Skip to main content
Glama
Sign In
monarch-mcp-server

monarch-mcp-server

by robcerda
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

get_cashflow

Analyze cashflow by providing start and end dates in YYYY-MM-DD format to evaluate financial trends and transactions within a specified period.

Instructions

Get cashflow analysis from Monarch Money.

Args:
    start_date: Start date in YYYY-MM-DD format
    end_date: End date in YYYY-MM-DD format

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

NameRequiredDescriptionDefault
end_dateNo
start_dateNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states this is a 'Get' operation, implying read-only behavior, but doesn't disclose any behavioral traits such as authentication requirements, rate limits, data freshness, or what constitutes a cashflow analysis. This leaves significant gaps for a tool with no annotation coverage.

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 appropriately sized with two sentences: one stating the purpose and one listing parameters. It's front-loaded with the main function, though the parameter listing could be integrated more smoothly. There's minimal waste, earning its place efficiently.

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?

Given the complexity of financial analysis tools, no annotations, no output schema, and 0% schema coverage, the description is incomplete. It lacks details on authentication needs, return format, error handling, and how cashflow analysis is defined, making it inadequate for informed tool selection and invocation.

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 description adds meaningful semantics by specifying the date format (YYYY-MM-DD) for both parameters, which compensates for the 0% schema description coverage. However, it doesn't explain default behaviors (e.g., what happens if dates are null) or constraints like valid date ranges, leaving some ambiguity.

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

Purpose4/5

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

The description clearly states the verb 'Get' and resource 'cashflow analysis from Monarch Money', providing a specific purpose. However, it doesn't distinguish this tool from sibling tools like 'get_transactions' or 'get_accounts', which might also retrieve financial data, so it doesn't fully differentiate from alternatives.

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?

The description provides no guidance on when to use this tool versus alternatives like 'get_transactions' or 'get_accounts', nor does it mention prerequisites such as authentication status. It only lists parameters without context on appropriate usage scenarios.

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

Deploy Server

Other Tools

Related Tools