Skip to main content
Glama
Sign In
Rocket Money MCP

Rocket Money MCP

by aidanouckama
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

get_account

Read-onlyIdempotent

Retrieve a single Rocket Money account’s balance, statement balance, minimum payment, and due date by supplying its account ID.

Instructions

Read one account’s balance, statement balance, minimum payment and due date when supplied by Rocket Money.

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_id": "<account_id>"
    },
    "name": "get_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
account_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description adds real value with 'when supplied by Rocket Money,' warning that some fields may legitimately be absent, but it says nothing about behavior for an unknown or unauthorized account_id.

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 sentence with the returned fields front-loaded and no filler; every clause carries information the agent needs.

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?

A simple single-parameter read tool whose annotations cover the safety profile and whose description covers the payload, including conditional availability of fields. The remaining gap is practical guidance on sourcing and validating the account_id, which neither the schema nor the description supplies.

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?

Only one parameter and its schema description coverage is 0%, so the description must compensate and only partially does — 'one account' implies the ID identifies a single record. It does not explain the expected ID format or that IDs come from list_accounts.

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?

Specific verb and resource: 'Read one account' scoped to a single record, plus an enumeration of the returned fields (balance, statement balance, minimum payment, due date). The singular 'one account' implicitly contrasts with list_accounts, but no sibling is named explicitly.

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 phrase 'Read one account' implies this is for fetching a single known account rather than enumerating them, which points an agent toward list_accounts for discovery. However, it never states that condition outright or mentions prerequisites such as obtaining the account_id first.

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