monarchmoney-node

is_refresh_complete

Check whether a Monarch Money account refresh has finished. Specify account IDs to monitor specific accounts or omit to check all.

Instructions

Check whether a previously started account refresh has completed.

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": "is_refresh_complete"
  }
}

Input Schema

Name	Required	Description	Default
`account_ids`	No	Account IDs to check. Omit to check all.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.1May 28, 2026

TDQS

B3.4/5.0

Behavior3/5

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

With no annotations, the description must disclose behavior. It states the check operation but does not mention what happens if no refresh was started, whether it's idempotent, or rate limits. Adequate for a simple read operation but lacks depth.

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, no extraneous words, front-loaded with the essential purpose.

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?

No output schema and no description of return value (e.g., boolean or status object). For a check tool, the outcome is critical. The description is too minimal for complete understanding.

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 covers 100% of parameters with good description. Description adds minimal value beyond schema, just indicating the context of 'previously started account refresh'.

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 action 'check' and the specific resource 'whether a previously started account refresh has completed'. It differentiates from sibling tools like refresh_accounts and get_accounts.

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?

No guidance on when to use this tool versus alternatives (e.g., polling after refresh_accounts). Does not specify prerequisites or conditions for checking.

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