Skip to main content
Glama
MoneyFlow MCP Server

MoneyFlow MCP Server

find_transactions

Query personal finance transactions within a date range, then filter by account or by text in the description or comment to locate matching ledger entries.

Instructions

Transactions with their ledger entry. text is a case-insensitive substring of description or comment.

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": {
      "date_from": "<date_from>",
      "date_to": "<date_to>"
    },
    "name": "find_transactions"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNo
limitNo
date_toYes
date_fromYes
account_idNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

With no annotations, the description carries the full burden and discloses almost nothing: it does not confirm this is a read-only lookup, does not mention result ordering, pagination, or what `limit` defaults to (20). It does add one useful behavioral detail — that `text` matches description or comment case-insensitively — but that is parameter-level, not tool-level.

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?

Two short sentences with no filler, and the most distinctive detail (substring matching semantics) is stated up front. It is under-specified rather than bloated, so brevity itself is not the flaw.

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?

An output schema exists, so return values need not be explained, but for a 5-parameter query tool with zero schema coverage the description leaves date format, account scoping, and limit/pagination behavior unaddressed. An agent could not construct a correct call from this text plus schema alone.

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 0% across 5 parameters, so the description must compensate and it only covers one: `text`. The required `date_from`/`date_to` (format, inclusivity), `account_id`, and `limit` behavior are entirely undocumented anywhere.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Transactions with their ledger entry" describes the returned resource and implies a lookup, but never states the filtering/query verb or that results are scoped by the required date range. It gives no differentiation from siblings spending and category_totals, so an agent must infer this is the raw-transaction search vs. the aggregate tools.

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 spending or category_totals, and no mention of the required date range as a precondition. The only usage hint is an implicit one embedded in the `text` explanation.

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