monarchmoney-node

refresh_accounts

Trigger a refresh of account balances and transactions from linked financial institutions. Non-blocking action updates data.

Instructions

Trigger a refresh of account balances and transactions from linked institutions. Non-blocking.

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": {
      "account_ids": "<account_ids>"
    },
    "name": "refresh_accounts"
  }
}

Input Schema

Name	Required	Description	Default
`account_ids`	Yes	Account IDs to refresh

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.1May 28, 2026

TDQS

B3.3/5.0

Behavior2/5

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

With no annotations, the description carries full burden but only mentions 'Non-blocking', omitting details like asynchronous processing, potential delays, or failure modes. More behavioral context is needed.

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 concise sentence, front-loaded with the action verb, with no filler or repetition. Every word contributes to the core purpose.

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 low complexity, the description covers the basic purpose and non-blocking nature, but fails to mention the need to check is_refresh_complete or that refresh may take time, leaving gaps for effective use.

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% with clear parameter description, and the description adds minimal context ('from linked institutions'), achieving baseline. No extra syntax or constraints are provided beyond the schema.

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 'Trigger a refresh' and the resource 'account balances and transactions from linked institutions', distinguishing it from read-only sibling tools like get_accounts or get_transactions.

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, such as using is_refresh_complete to check status or avoiding duplicate triggers. The description lacks context for proper invocation.

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