Skip to main content
Glama
Sign In
monarchmoney-node

monarchmoney-node

by hakimelek
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_recent_account_balances

Retrieve daily balances for your Monarch Money accounts over a specified date range. Defaults to the past 31 days if no start date is provided.

Instructions

Get daily account balances for a date range. Defaults to last 31 days.

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

Input Schema

NameRequiredDescriptionDefault
start_dateNoStart date in YYYY-MM-DD format. Defaults to 31 days ago.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

B3.2/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 full burden. It discloses the read-only nature and date-range constraint but omits details about data freshness, pagination, permissions, or what constitutes 'balances' (e.g., pending entries). This lack of depth leaves the agent underinformed.

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?

A single, front-loaded sentence that contains no filler. Every word serves a purpose: verb, resource, scope, and default behavior.

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 tool's simplicity (one optional param, no output schema, no annotations), the description is minimally adequate. However, it fails to describe the return format (e.g., list of daily balances per account) or how to interpret the results, which would help the agent use the output properly.

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% and the schema already describes the 'start_date' parameter and its default. The tool description echoes this default ('last 31 days'), adding no new semantic value beyond the schema.

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 action (get), resource (daily account balances), and scope (date range). It distinguishes from siblings like 'get_accounts' (current balances) and 'get_account_history' (transactions), but does not explicitly contrast with them.

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 when to use (need daily balances over a range) and provides a default, but offers no explicit guidance on when not to use or alternatives among the many sibling tools.

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