Bankstatemently

Compare Transaction Groups

compare

Read-only

Side-by-side metric comparison for two filtered groups of transactions (e.g. one category vs another, one month vs another). 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 + identityKey); "dateRange" bounds by transaction date (YYYY-MM-DD).
`metric`	Yes	Metric for both groups.
`filterA`	Yes	Subset of transactions to operate on. All fields are optional and combined with AND logic.
`filterB`	Yes	Subset of transactions to operate on. All fields are optional and combined with AND logic.

Output Schema

TableJSON Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

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

Changed32 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 / filterA / description

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

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

addedInput schema / properties / filterA / properties / category / description

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

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

addedInput schema / properties / filterA / properties / merchant / description

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

addedInput schema / properties / filterA / properties / text / description

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

addedInput schema / properties / filterB / description

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

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

addedInput schema / properties / filterB / properties / category / description

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

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

addedInput schema / properties / filterB / properties / merchant / description

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

addedInput schema / properties / filterB / properties / text / description

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

addedInput schema / properties / metric / description
```
Added value: +"Metric for both groups."
```

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"

Changed30 schema fields changedAug 21, 2026

removedInput schema / properties / filterA / description

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

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

removedInput schema / properties / filterA / properties / category / description

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

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

removedInput schema / properties / filterA / properties / merchant / description

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

removedInput schema / properties / filterA / properties / text / description

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

removedInput schema / properties / filterB / description

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

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

removedInput schema / properties / filterB / properties / category / description

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

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

removedInput schema / properties / filterB / properties / merchant / description

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

removedInput schema / properties / filterB / properties / text / description

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

removedInput schema / properties / metric / description
```
Removed value: -"Metric for both groups."
```

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.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description adds the default-scope behavior ('Scope defaults to all your completed statements') and the ability to narrow via 'scope'. This is meaningful context beyond the annotations, though it does not address rate limits or auth, which are less critical given the read-only safety profile.

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?

The description is two sentences with zero filler. The core purpose is front-loaded, and the scope behavior is stated efficiently. Every word earns its place, making it highly concise and well-structured.

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?

For a tool with 4 parameters (including nested objects) and an output schema, the description is reasonably complete. It explains the default scope and the general comparison intent, and the schema covers parameter details. It does not mention edge cases or limitations (e.g., max number of results), but these are minor given the read-only nature and output schema.

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 description coverage is 100%, so the baseline is 3. The description adds a usage example ('one category vs another') that clarifies the intended semantics of filterA/filterB, and it explains the default scope for the 'scope' parameter. However, it does not significantly compensate beyond what the schema already documents, so a 3 is appropriate.

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's function: 'Side-by-side metric comparison for two filtered groups of transactions' and provides concrete examples ('one category vs another, one month vs another'). This distinguishes it from siblings like aggregate (single group) and group_by (grouping), making its purpose unambiguous.

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?

The description implies usage by its clear definition and examples, but does not explicitly state when to prefer this over alternatives (e.g., aggregate for one group). It does provide context on the default scope and how to narrow it, which aids decision-making, though it lacks explicit exclusion criteria.

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.