Skip to main content
Glama
Sign In
Rocket Money MCP

Rocket Money MCP

by aidanouckama
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

list_transactions

Read-onlyIdempotent

Reads one page of merchant-level purchases for a date range, using a cursor to paginate through all results. Filter by account or query, and receive amounts in integer cents.

Instructions

Read ONE page of merchant-level purchases for a date range. Follow nextCursor until hasMore=false with identical filters. No global row limit. Values are integer cents; flags/currency may be null. No receipt line items.

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": {
      "since": "<since>",
      "before": "<before>"
    },
    "name": "list_transactions"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNo
sinceYesInclusive start date.
beforeYesExclusive end date. For all November use 2026-11-01 to 2026-12-01.
cursorNoOpaque nextCursor from the previous response; keep all filters identical.
page_sizeNoDefault 100. Keep unchanged when following nextCursor.
account_idsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, open-world, non-destructive, so the bar is lower, and the description still adds substantial context: unbounded result sets requiring cursor loops, no global row limit, integer-cent values, potentially null flags/currency, and the absence of receipt line items. These are behavioral facts an agent cannot get from the structured fields.

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?

Four short sentences, front-loaded with the one-page paging model, followed by iteration instructions and output-format caveats. Every sentence carries operational information; there is no filler.

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?

With no output schema, the description usefully names hasMore/nextCursor and explains value units and nullability, which is what an agent needs to consume results. It stops short of explaining how account_ids filtering behaves when omitted, or what fields a transaction record contains, but the critical call-and-iterate contract is complete.

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 67%, so the schema already documents since, before, cursor and page_size. The description reinforces cursor stability (identical filters) but adds no meaning for query or account_ids, leaving the filter semantics largely to the schema. Baseline 3 is appropriate at this coverage level.

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?

States a specific verb and resource (read merchant-level purchases over a date range) plus the key scope constraint that it returns exactly ONE page. The resource is distinct enough from siblings like list_accounts and list_categories that an agent can route correctly without ambiguity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit operational guidance for the follow-up call: continue with nextCursor until hasMore=false while keeping filters identical. It does not cover when to prefer a different tool or what happens when filters change mid-pagination, but the usage context it does provide is clear and actionable.

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