Bankstatemently

Group Transactions

group_by

Read-only

Group transactions by a dimension (month/category/counterparty/account/currency) and apply a metric to each group. Results are per-currency. The "counterparty" dimension keys on the printed counterparty, else a printed account mask (••1234), else the description's name tokens, so a rail word or reference number never splits one payee; a line with no key groups under "unknown". Scope defaults to all your completed statements; pass "scope" to narrow to specific accounts/products and/or a date range.

Input Schema

TableJSON Schema

Name	Required	Description
`scope`	No	Optional structural scope (WHO × WHEN). Omit to search across all your completed statements. "accounts" is a list of account/product chips ({ kind: "account" \| "product", id }, the id of an account descriptor or product returned by a tool); "dateRange" bounds by transaction date (YYYY-MM-DD).
`filter`	No	Subset of transactions to operate on. All fields are optional and combined with AND logic.
`metric`	Yes	Metric per group.
`dimension`	Yes	Grouping dimension.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`scope`	Yes
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 6, 2026

changedInput schema / properties / dimension / enum

Previous value: -[
-  "month",
-  "category",
-  "merchant",
-  "account",
-  "currency"
-]New value: +[
+  "month",
+  "category",
+  "counterparty",
+  "account",
+  "currency"
+]

Changed5 schema fields changedOct 2, 2026

addedInput schema / properties / filter / additionalProperties
```
Added value: +false
```

removedInput schema / properties / filter / properties / accounts

Removed value: -{
-  "description": "Account number slugs to include.",
-  "items": {
-    "type": "string"
-  },
-  "type": "array"
-}

changedInput schema / properties / scope / description

Previous 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)."New value: +"Optional structural scope (WHO × WHEN). Omit to search across all your completed statements. \"accounts\" is a list of account/product chips ({ kind: \"account\" | \"product\", id }, the id of an account descriptor or product returned by a tool); \"dateRange\" bounds by transaction date (YYYY-MM-DD)."

changedInput schema / properties / scope / properties / accounts / description

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

changedInput schema / properties / scope / properties / accounts / items / oneOf

Previous 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"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "id": {
+        "description": "The account id: the `id` of an account descriptor returned by a tool, or of a statement tool `accounts[]` entry.",
+        "format": "uuid",
+        "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
+        "type": "string"
+      },
+      "kind": {
+        "const": "account",
+        "description": "This chip addresses a single account.",
+        "type": "string"
+      }
+    },
+    "required": [
+      "kind",
+      "id"
+    ],
+    "type": "object"
+  },
+  {
+    "additionalProperties": false,
+    "properties": {
+      "id": {
+        "description": "The product id: the `id` of a product returned by a statement tool (`get_statement` / `convert_statement`, `products[].id`).",
+        "format": "uuid",
+        "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
+        "type": "string"
+      },
+      "kind": {
+        "const": "product",
+        "description": "This chip addresses a product and expands to its child accounts.",
+        "type": "string"
+      }
+    },
+    "required": [
+      "kind",
+      "id"
+    ],
+    "type": "object"
+  }
+]

Changed3 schema fields changedSep 10, 2026

addedOutput schema / $defs

Added value: +{
+  "__schema0": {
+    "anyOf": [
+      {
+        "type": "string"
+      },
+      {
+        "type": "number"
+      },
+      {
+        "type": "boolean"
+      },
+      {
+        "type": "null"
+      },
+      {
+        "items": {
+          "$ref": "#/$defs/__schema0"
+        },
+        "type": "array"
+      },
+      {
+        "additionalProperties": {
+          "$ref": "#/$defs/__schema0"
+        },
+        "propertyNames": {
+          "type": "string"
+        },
+        "type": "object"
+      }
+    ]
+  }
+}

changedOutput schema / properties / result / anyOf

Previous value: -[
-  {
-    "additionalProperties": {},
-    "properties": {},
-    "type": "object"
-  },
-  {
-    "items": {
-      "additionalProperties": {},
-      "properties": {},
-      "type": "object"
-    },
-    "type": "array"
-  }
-]New value: +[
+  {
+    "additionalProperties": {
+      "$ref": "#/$defs/__schema0"
+    },
+    "propertyNames": {
+      "type": "string"
+    },
+    "type": "object"
+  },
+  {
+    "items": {
+      "additionalProperties": {
+        "$ref": "#/$defs/__schema0"
+      },
+      "propertyNames": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    "type": "array"
+  }
+]

changedOutput schema / properties / scope / additionalProperties
```
Previous value: -{}New value: +false
```

Changed22 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 / dimension / description
```
Added value: +"Grouping dimension."
```

addedInput schema / properties / filter / description

Added value: +"Subset of transactions to operate on. All fields are optional and combined with AND logic."

addedInput schema / properties / filter / properties / accounts / description
```
Added value: +"Account number slugs to include."
```
addedInput schema / properties / filter / properties / amountMax / description
```
Added value: +"Inclusive maximum absolute amount."
```
addedInput schema / properties / filter / properties / amountMin / description
```
Added value: +"Inclusive minimum absolute amount."
```

addedInput schema / properties / filter / properties / category / description

Added value: +"Category slug, e.g. \"meals_entertainment\", \"groceries_personal\"."

addedInput schema / properties / filter / properties / currency / description
```
Added value: +"ISO 4217 currency code. E.g. \"USD\", \"HKD\"."
```
addedInput schema / properties / filter / properties / dateEnd / description
```
Added value: +"ISO date (YYYY-MM-DD). Inclusive upper bound."
```
addedInput schema / properties / filter / properties / dateStart / description
```
Added value: +"ISO date (YYYY-MM-DD). Inclusive lower bound."
```
addedInput schema / properties / filter / properties / direction / description
```
Added value: +"Semantic direction."
```

addedInput schema / properties / filter / properties / merchant / description

Added value: +"Substring match against description or counterparty (case-insensitive)."

addedInput schema / properties / filter / properties / text / description

Added value: +"Whole-row text search over raw transaction fields (case-insensitive)."

addedInput schema / properties / metric / description
```
Added value: +"Metric per group."
```

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"

Changed20 schema fields changedAug 21, 2026

removedInput schema / properties / dimension / description
```
Removed value: -"Grouping dimension."
```

removedInput schema / properties / filter / description

Removed value: -"Subset of transactions to operate on. All fields are optional and combined with AND logic."

removedInput schema / properties / filter / properties / accounts / description
```
Removed value: -"Account number slugs to include."
```
removedInput schema / properties / filter / properties / amountMax / description
```
Removed value: -"Inclusive maximum absolute amount."
```
removedInput schema / properties / filter / properties / amountMin / description
```
Removed value: -"Inclusive minimum absolute amount."
```

removedInput schema / properties / filter / properties / category / description

Removed value: -"Category slug, e.g. \"meals_entertainment\", \"groceries_personal\"."

removedInput schema / properties / filter / properties / currency / description
```
Removed value: -"ISO 4217 currency code. E.g. \"USD\", \"HKD\"."
```
removedInput schema / properties / filter / properties / dateEnd / description
```
Removed value: -"ISO date (YYYY-MM-DD). Inclusive upper bound."
```
removedInput schema / properties / filter / properties / dateStart / description
```
Removed value: -"ISO date (YYYY-MM-DD). Inclusive lower bound."
```
removedInput schema / properties / filter / properties / direction / description
```
Removed value: -"Semantic direction."
```

removedInput schema / properties / filter / properties / merchant / description

Removed value: -"Substring match against description or counterparty (case-insensitive)."

removedInput schema / properties / filter / properties / text / description

Removed value: -"Whole-row text search over raw transaction fields (case-insensitive)."

removedInput schema / properties / metric / description
```
Removed value: -"Metric per group."
```

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."
```

First observedAug 12, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Adds substantial behavior beyond the readOnly/destructive/openWorld annotations: results are computed per-currency, the counterparty keying fallback chain (printed counterparty, then account mask, then description name tokens) so rail words or reference numbers never split a payee, and unkeyed lines land in an "unknown" bucket. These are exactly the traits an agent needs to interpret output correctly.

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?

Front-loads the purpose, then layers in the per-currency caveat and scope default. Three sentences with no filler, though the counterparty sentence is clause-heavy and could be split for faster scanning.

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?

An output schema exists so return shape needn't be explained; the description covers the non-obvious semantics (per-currency results, default scope, unknown bucket) that an agent would otherwise guess wrong. Minor gaps remain around pagination/limits and how metrics behave across multiple currencies in one result set.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning for the ambiguous enum value: it defines how "counterparty" is keyed and what happens when no key exists, plus the default behavior of the optional scope object. It adds nothing for metric or filter, keeping it short of a 5.

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 (group), resource (transactions), the exact grouping axes, and the metric applied per group, which lets an agent separate it from aggregate, time_series, and top_n without opening a schema. The enumerated dimensions map directly to the required parameter.

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 concrete operating context: scope defaults to all completed statements, and passing "scope" narrows to accounts/products and/or a date range. It never names a sibling alternative or states when another tool would be the better choice, so the guidance is clear but not exclusionary.

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.