Skip to main content
Glama

Bankstatemently

by io.github.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
NameRequiredDescriptionDefault
scopeNoOptional 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).
metricYesMetric for both groups.
filterAYesSubset of transactions to operate on. All fields are optional and combined with AND logic.
filterBYesSubset of transactions to operate on. All fields are optional and combined with AND logic.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
scopeYes
resultYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed32 schema fields changed
    • 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"
  2. Changed30 schema fields changed
    • 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."
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true and destructiveHint=false, so no safety contradiction exists. The description adds useful behavioral context by explaining that the default scope is all completed statements and that the scope parameter can narrow by accounts/products and date range. This is meaningful beyond the structured annotations.

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 concise sentences with the core purpose front-loaded. The examples are useful and the scoping note is directly actionable. Every sentence earns its place with no redundancy or fluff.

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 nested parameters, an output schema, and multiple aggregation siblings, this definition covers the essential behavioral and scoping facts. It could be slightly stronger by explicitly stating when to choose compare over aggregate or group_by, but the description plus schema is sufficient for correct invocation.

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 schema already documents all parameters in detail. The description mentions 'scope' and gives examples of filter groups, but it does not add meaningful parameter semantics beyond what the schema provides. Baseline 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 states a specific action ('Side-by-side metric comparison') on a clear resource ('two filtered groups of transactions') and gives concrete examples ('one category vs another, one month vs another'). This distinguishes it from sibling tools like aggregate, group_by, and top_n by emphasizing pairwise comparison.

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 clearly conveys when to use the tool: whenever two filtered transaction groups need comparison. It also provides scoping guidance ('Scope defaults to all your completed statements; pass "scope" to narrow...'). It does not explicitly name alternatives or exclusion conditions, but the use case is clear enough.

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

All Bankstatemently toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4/5.0
Disambiguation4/5

Core tools are cleanly separated by resource: statements, transactions, transfers, credits, and benchmark all have dedicated entry points. The five analytics tools (aggregate, group_by, compare, time_series, top_n) share metric/filter language, but their distinct output shapes and careful descriptions prevent major confusion, with only group_by vs. time_series/top_n occasionally overlapping.

Naming Consistency4/5

Most tools follow a clear snake_case verb_noun pattern such as convert_statement, list_transactions, rate_statement, and dismiss_statement. The analytics tools (aggregate, compare, group_by, time_series, top_n) break that pattern, but they are still recognizable, consistently styled, and form a meaningful cluster.

Tool Count4/5

At 16 tools, this is slightly above the typical 3-15 well-scoped range, but the server covers a broad workflow: upload, conversion, retrieval, categorization, analytics, transfer matching, rating, credits, and benchmarking. Each tool maps to a distinct capability, so the count feels justified rather than bloated.

Completeness4/5

The tool surface covers the full statement lifecycle from upload and conversion through retrieval, categorization, analysis, rating, and dismissal, plus useful side capabilities like credits and benchmark evaluation. Minor gaps exist—no permanent deletion and no way to manually edit category mappings—but dismiss_statement and categorize_statement provide adequate workarounds.

Resources