Skip to main content
Glama
Rocket Money MCP

Rocket Money MCP

by aidanouckama

list_accounts

Read-onlyIdempotent

Reads linked account balances in integer cents, connection status, and available sync timestamps so you can inspect account health and sync recency.

Instructions

Read linked account balances in integer cents, connection status and available sync timestamps. Missing values remain null.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already cover the safety profile: readOnly, idempotent, non-destructive, and open-world. The description adds only a detail about the data display: units and null handling; it does not say whether balances are cached or live, how they are ordered, or whether they are paginated. It adds useful detail but leaves some behavior unspecified.

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?

Two short sentences with no filler; the returned fields are listed first, and the null-handling caveat follows. Every clause adds useful information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Because there is no output schema, the description has to imply the shape of the response. It does name the key fields and their units, which is a solid basis for a zero-parameter read tool. Gaps remain around ordering, pagination, and per-connection grouping.

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 tool has zero parameters and a fully described schema, so nothing needs to be explained. The description correctly avoids restating an empty input contract.

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 uses a specific verb ('Read') and resource ('linked account balances') and enumerates the returned fields: balances in integer cents, connection status, and sync timestamps. It does not distinguish this tool from the sibling get_account or list_transactions, which would require more explicit scope language.

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 a bulk listing of linked accounts and says nothing about when to prefer get_account for a single account or list_transactions for activity. There are no exclusions and no alternatives, so the agent must infer the choice from the name alone.

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