Bankstatemently

Match Transfers Between Accounts

list_transfers

Read-only

Match transfers between your own accounts. A transfer is TWO transactions — a debit leaving one of your accounts and a credit arriving in another — matched as two sides of the same movement (amount and date aligned); account-level successions (an account closing into a successor) are matched too. A payment to an outside party is not a transfer here: only movements with both sides visible in your statements are matched. THE way to answer any "was money moved between my accounts" / "did I transfer X" question — never try to answer a money-moved-between-accounts question with list_transactions + arithmetic; always call this tool instead. Scope defaults to all your completed statements; pass "scope" to narrow to specific accounts/products and/or a date range. Every response reports the match window (in days) it used, even when no transfers are found — a lack of matches is never silent about how hard it looked. To find large movements with NO matching counterpart in your other accounts — e.g. "trace transfers over $10,000; which ones leave without a known destination?" — pass "amountMin": reconciled pairs and successions are filtered to that floor, and the response gains an "unmatched" bucket of large movements (debits leaving, or unexplained credits arriving) with no matching pair, candidate, or succession. Omit amountMin for the ordinary reconciled-pairs answer.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`scope`	No	Optional structural scope (WHO × WHEN). Omit to search across all your completed statements. "accounts" is a list of account/product chips (kind + identityKey); "dateRange" bounds by transaction date (YYYY-MM-DD).
`amountMin`	No	Inclusive minimum absolute amount. When present, transfers/accountSuccessions are floored to this amount and the response gains an "unmatched" bucket of large movements with no matching counterpart. Omit for the ordinary reconciled-pairs answer.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`scope`	Yes
`ambiguous`	Yes
`transfers`	Yes
`unmatched`	No
`ambiguousCount`	Yes
`matchWindowDays`	Yes
`accountSuccessions`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed35 schema fields changedSep 10, 2026

changedOutput schema / properties / accountSuccessions / items / additionalProperties
```
Previous value: -{}New value: +false
```
addedOutput schema / properties / accountSuccessions / items / properties / currency
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / accountSuccessions / items / properties / effectiveDate
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / accountSuccessions / items / properties / predecessorAccount
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / accountSuccessions / items / properties / predecessorDropAmount
```
Added value: +{
+  "type": "number"
+}
```
addedOutput schema / properties / accountSuccessions / items / properties / provenance
```
Added value: +{
+  "const": "deterministic",
+  "type": "string"
+}
```
addedOutput schema / properties / accountSuccessions / items / properties / successorAccounts
```
Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
```
addedOutput schema / properties / accountSuccessions / items / properties / successorOpeningAmount
```
Added value: +{
+  "type": "number"
+}
```

addedOutput schema / properties / accountSuccessions / items / required

Added value: +[
+  "predecessorAccount",
+  "successorAccounts",
+  "currency",
+  "predecessorDropAmount",
+  "successorOpeningAmount",
+  "effectiveDate",
+  "provenance"
+]

changedOutput schema / properties / ambiguous / items / additionalProperties
```
Previous value: -{}New value: +false
```
addedOutput schema / properties / ambiguous / items / properties / amount
```
Added value: +{
+  "type": "number"
+}
```
addedOutput schema / properties / ambiguous / items / properties / currency
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / ambiguous / items / properties / fromAccount
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / ambiguous / items / properties / fromDate
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / ambiguous / items / properties / fromTransactionId
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / ambiguous / items / properties / toAccount
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / ambiguous / items / properties / toDate
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / ambiguous / items / properties / toTransactionId
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / ambiguous / items / required

Added value: +[
+  "fromAccount",
+  "toAccount",
+  "fromTransactionId",
+  "toTransactionId",
+  "amount",
+  "currency",
+  "fromDate",
+  "toDate"
+]

changedOutput schema / properties / scope / additionalProperties
```
Previous value: -{}New value: +false
```
changedOutput schema / properties / transfers / items / additionalProperties
```
Previous value: -{}New value: +false
```
addedOutput schema / properties / transfers / items / properties / amount
```
Added value: +{
+  "type": "number"
+}
```
addedOutput schema / properties / transfers / items / properties / currency
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / transfers / items / properties / dateDeltaDays
```
Added value: +{
+  "type": "number"
+}
```
addedOutput schema / properties / transfers / items / properties / fromAccount
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / transfers / items / properties / fromDate
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / transfers / items / properties / provenance

Added value: +{
+  "enum": [
+    "deterministic",
+    "judge"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / transfers / items / properties / toAccount
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / transfers / items / properties / toDate
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / transfers / items / required

Added value: +[
+  "fromAccount",
+  "toAccount",
+  "amount",
+  "currency",
+  "fromDate",
+  "toDate",
+  "dateDeltaDays",
+  "provenance"
+]

changedOutput schema / properties / unmatched / additionalProperties
```
Previous value: -{}New value: +false
```
addedOutput schema / properties / unmatched / properties / count
```
Added value: +{
+  "type": "number"
+}
```
addedOutput schema / properties / unmatched / properties / floorAmount
```
Added value: +{
+  "type": "number"
+}
```

addedOutput schema / properties / unmatched / properties / movements

Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "account": {
+        "type": "string"
+      },
+      "amount": {
+        "type": "number"
+      },
+      "currency": {
+        "type": "string"
+      },
+      "date": {
+        "type": "string"
+      },
+      "description": {
+        "type": "string"
+      },
+      "direction": {
+        "enum": [
+          "credit",
+          "debit"
+        ],
+        "type": "string"
+      },
+      "sourceDocument": {
+        "additionalProperties": false,
+        "properties": {
+          "contentHash": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          }
+        },
+        "required": [
+          "contentHash"
+        ],
+        "type": "object"
+      }
+    },
+    "required": [
+      "account",
+      "date",
+      "description",
+      "amount",
+      "currency",
+      "direction",
+      "sourceDocument"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / unmatched / required

Added value: +[
+  "floorAmount",
+  "count",
+  "movements"
+]

Changed10 schema fields changedSep 4, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedInput schema / properties / amountMin / description

Added value: +"Inclusive minimum absolute amount. When present, transfers/accountSuccessions are floored to this amount and the response gains an \"unmatched\" bucket of large movements with no matching counterpart. Omit for the ordinary reconciled-pairs answer."

addedInput schema / properties / scope / description

Added value: +"Optional structural scope (WHO × WHEN). Omit to search across all your completed statements. \"accounts\" is a list of account/product chips (kind + identityKey); \"dateRange\" bounds by transaction date (YYYY-MM-DD)."

addedInput schema / properties / scope / properties / accounts / description

Added value: +"Account/product chips (kind + identityKey) to scope to. Empty = all accounts."

removedInput schema / properties / scope / properties / accounts / items / anyOf

Removed value: -[
-  {
-    "properties": {
-      "anchorContentHash": {
-        "type": "string"
-      },
-      "identityKey": {
-        "minLength": 1,
-        "type": "string"
-      },
-      "kind": {
-        "const": "account",
-        "type": "string"
-      },
-      "label": {
-        "type": "string"
-      }
-    },
-    "required": [
-      "kind",
-      "identityKey"
-    ],
-    "type": "object"
-  },
-  {
-    "properties": {
-      "identityKey": {
-        "minLength": 1,
-        "type": "string"
-      },
-      "kind": {
-        "const": "product",
-        "type": "string"
-      },
-      "label": {
-        "type": "string"
-      }
-    },
-    "required": [
-      "kind",
-      "identityKey"
-    ],
-    "type": "object"
-  }
-]

addedInput schema / properties / scope / properties / accounts / items / oneOf

Added value: +[
+  {
+    "properties": {
+      "anchorContentHash": {
+        "description": "Document-anchored lookup when present (results page); omit for a user-scoped lookup (workspace surfaces).",
+        "type": "string"
+      },
+      "identityKey": {
+        "description": "Canonical account identity key (accountIdentityKey), never a raw DB UUID.",
+        "minLength": 1,
+        "type": "string"
+      },
+      "kind": {
+        "const": "account",
+        "description": "This chip addresses a single account.",
+        "type": "string"
+      },
+      "label": {
+        "description": "Display label for this chip.",
+        "type": "string"
+      }
+    },
+    "required": [
+      "kind",
+      "identityKey"
+    ],
+    "type": "object"
+  },
+  {
+    "properties": {
+      "identityKey": {
+        "description": "Product slug.",
+        "minLength": 1,
+        "type": "string"
+      },
+      "kind": {
+        "const": "product",
+        "description": "This chip addresses a product and expands to its child accounts.",
+        "type": "string"
+      },
+      "label": {
+        "description": "Display label for this chip.",
+        "type": "string"
+      }
+    },
+    "required": [
+      "kind",
+      "identityKey"
+    ],
+    "type": "object"
+  }
+]

addedInput schema / properties / scope / properties / dateRange / description

Added value: +"Bounds results to transactions within this date range. Omit for no date filter."

addedInput schema / properties / scope / properties / dateRange / properties / from / description
```
Added value: +"Start of the date range (inclusive), YYYY-MM-DD."
```
addedInput schema / properties / scope / properties / dateRange / properties / to / description
```
Added value: +"End of the date range (inclusive), YYYY-MM-DD."
```

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

Changed8 schema fields changedAug 21, 2026

removedInput schema / properties / amountMin / description

Removed value: -"Inclusive minimum absolute amount. When present, transfers/accountSuccessions are floored to this amount and the response gains an \"unmatched\" bucket of large movements with no matching counterpart. Omit for the ordinary reconciled-pairs answer."

removedInput schema / properties / scope / description

Removed value: -"Optional structural scope (WHO × WHEN). Omit to search across all your completed statements. \"accounts\" is a list of account/product chips (kind + identityKey); \"dateRange\" bounds by transaction date (YYYY-MM-DD)."

removedInput schema / properties / scope / properties / accounts / description

Removed value: -"Account/product chips (kind + identityKey) to scope to. Empty = all accounts."

addedInput schema / properties / scope / properties / accounts / items / anyOf

Added value: +[
+  {
+    "properties": {
+      "anchorContentHash": {
+        "type": "string"
+      },
+      "identityKey": {
+        "minLength": 1,
+        "type": "string"
+      },
+      "kind": {
+        "const": "account",
+        "type": "string"
+      },
+      "label": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "kind",
+      "identityKey"
+    ],
+    "type": "object"
+  },
+  {
+    "properties": {
+      "identityKey": {
+        "minLength": 1,
+        "type": "string"
+      },
+      "kind": {
+        "const": "product",
+        "type": "string"
+      },
+      "label": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "kind",
+      "identityKey"
+    ],
+    "type": "object"
+  }
+]

removedInput schema / properties / scope / properties / accounts / items / oneOf

Removed value: -[
-  {
-    "properties": {
-      "anchorContentHash": {
-        "description": "Document-anchored lookup when present (results page); omit for a user-scoped lookup (workspace surfaces).",
-        "type": "string"
-      },
-      "identityKey": {
-        "description": "Canonical account identity key (accountIdentityKey), never a raw DB UUID.",
-        "minLength": 1,
-        "type": "string"
-      },
-      "kind": {
-        "const": "account",
-        "description": "This chip addresses a single account.",
-        "type": "string"
-      },
-      "label": {
-        "description": "Display label for this chip.",
-        "type": "string"
-      }
-    },
-    "required": [
-      "kind",
-      "identityKey"
-    ],
-    "type": "object"
-  },
-  {
-    "properties": {
-      "identityKey": {
-        "description": "Product slug.",
-        "minLength": 1,
-        "type": "string"
-      },
-      "kind": {
-        "const": "product",
-        "description": "This chip addresses a product and expands to its child accounts.",
-        "type": "string"
-      },
-      "label": {
-        "description": "Display label for this chip.",
-        "type": "string"
-      }
-    },
-    "required": [
-      "kind",
-      "identityKey"
-    ],
-    "type": "object"
-  }
-]

removedInput schema / properties / scope / properties / dateRange / description

Removed value: -"Bounds results to transactions within this date range. Omit for no date filter."

removedInput schema / properties / scope / properties / dateRange / properties / from / description
```
Removed value: -"Start of the date range (inclusive), YYYY-MM-DD."
```
removedInput schema / properties / scope / properties / dateRange / properties / to / description
```
Removed value: -"End of the date range (inclusive), YYYY-MM-DD."
```

Changed2 schema fields changedAug 13, 2026

addedInput schema / properties / amountMin

Added value: +{
+  "description": "Inclusive minimum absolute amount. When present, transfers/accountSuccessions are floored to this amount and the response gains an \"unmatched\" bucket of large movements with no matching counterpart. Omit for the ordinary reconciled-pairs answer.",
+  "type": "number"
+}

addedOutput schema / properties / unmatched

Added value: +{
+  "additionalProperties": {},
+  "properties": {},
+  "type": "object"
+}

First observedAug 12, 2026

TDQS

A4.6/5.0

Behavior5/5

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

The annotations declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds valuable behavioral context beyond that: it explains that the tool reports the match window used even when no transfers are found, ensuring no silent lack of results; and it details that with 'amountMin' the response includes an 'unmatched' bucket for large movements without a matching counterpart. This provides transparency about the tool's behavior and edge cases, which is not derivable from annotations alone.

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?

The description is relatively long but structured coherently, with the main purpose and key guidance front-loaded. It is dense with important information but avoids redundancy. Minor trimming could improve conciseness, but it is not bloated with fluff.

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

Completeness5/5

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

Given the tool's complexity (two-parameter, nested schema, output schema present), the description provides complete guidance: it defines what a transfer is, distinguishes from non-transfers, gives clear usage instructions, explains the effect of both parameters, and notes the tool always reports the match window. The output schema covers return values, so the description need not explain them. It lacks nothing an agent needs to call it correctly.

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?

The schema has 100% description coverage, so both parameters are documented in the schema. The description adds some context by explaining the effect of 'scope' (narrow to specific accounts/products and/or date range) and 'amountMin' (flooring transfers and adding unmatched bucket), but it doesn't add significant new meaning beyond what the schema already provides. The baseline 3 is appropriate as the schema does the heavy lifting.

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?

The description clearly states the tool matches transfers between the user's own accounts, defining a transfer as two transactions (debit and credit) matched by amount and date, plus account successions. It explicitly distinguishes from payments to outside parties, and it positions itself as the definitive tool for 'money moved between my accounts' questions, unlike list_transactions. This makes the purpose specific and unambiguous, and it differentiates from sibling tools like list_transactions.

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

Usage Guidelines5/5

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

The description explicitly instructs when to use this tool: 'THE way to answer any 'was money moved between my accounts' question' and 'never try to answer a money-moved-between-accounts question with list_transactions + arithmetic; always call this tool instead.' It also provides additional guidance on how to use the 'scope' parameter to narrow results and when to pass 'amountMin' for unmatched movements. This is explicit and actionable.

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

All Bankstatemently tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.