moneylover-mcp

Get Transactions

get_transactions

Retrieve transactions for a specified wallet across a date range using start and end dates in YYYY-MM-DD format to review activity.

Instructions

Fetch transactions for a wallet between two dates (YYYY-MM-DD).

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": {
      "walletId": "<walletId>",
      "startDate": "<startDate>",
      "endDate": "<endDate>"
    },
    "name": "get_transactions"
  }
}

Input Schema

Name	Required	Description
`token`	No	JWT token returned by login, or derived from environment credentials
`endDate`	Yes
`walletId`	Yes
`startDate`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 5, 2026

TDQS

C2.7/5.0

Behavior2/5

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

With no annotations at all, the description carries the full behavioral burden and discloses almost nothing: no indication of whether results are paginated, capped, sorted, or what authentication is required. The existence of a token parameter implies auth, but neither the description nor the annotations state that reads require a valid session.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence that covers the verb, the resource, and the scoping constraints with no wasted wording. Its brevity is efficient, though part of that economy comes from omitting necessary detail.

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?

There is no output schema and no annotations, so the description is the only source of return-value and safety information, and it supplies neither. For a four-parameter query tool with three required inputs, an agent cannot tell what comes back or how to page through large date ranges.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 25%, with just the token parameter documented in the schema. The description restates the YYYY-MM-DD format already enforced by the schema pattern for both dates and says nothing about what walletId accepts or how to obtain it, leaving the primary input unexplained.

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?

States a specific verb and resource (fetch transactions) scoped to a wallet and a date range, so an agent knows exactly what it retrieves. It does not distinguish itself from siblings like add_transaction or get_wallets, but the read-vs-write boundary is inferable from the verb.

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 versus get_wallets or get_categories, nor on where a walletId comes from or what to do if the range is large. The only usage hint is the date format, which is a parameter constraint rather than a when-to-use rule.

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

Deploy Server