Bankstatemently

List Statements

list_statements

Read-only

Browse your previously converted bank statements with pagination and optional status filter.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Max results (1-100)
`offset`	No	Pagination offset
`status`	No	Filter by status

Output Schema

TableJSON Schema

Name	Required	Description	Default
`documents`	Yes
`pagination`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 15, 2026
- removedOutput schema / properties / documents / items / properties / completedAt
```
Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ]
-}
```

Changed12 schema fields changedSep 10, 2026

addedOutput schema / properties / documents / items / properties / bank

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

addedOutput schema / properties / documents / items / properties / country

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

addedOutput schema / properties / documents / items / properties / currency
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / documents / items / properties / elapsedMs

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": false,
+      "properties": {
+        "pass": {
+          "type": "number"
+        },
+        "total": {
+          "type": "number"
+        }
+      },
+      "required": [
+        "pass",
+        "total"
+      ],
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

addedOutput schema / properties / documents / items / properties / error

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

addedOutput schema / properties / documents / items / properties / estimateSeconds

Added value: +{
+  "anyOf": [
+    {
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

addedOutput schema / properties / documents / items / properties / processingProgress

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": false,
+      "properties": {
+        "pagesProcessed": {
+          "type": "number"
+        },
+        "pass": {
+          "additionalProperties": false,
+          "properties": {
+            "number": {
+              "type": "number"
+            },
+            "startedAt": {
+              "type": "number"
+            }
+          },
+          "required": [
+            "number",
+            "startedAt"
+          ],
+          "type": "object"
+        },
+        "totalPages": {
+          "type": "number"
+        }
+      },
+      "required": [
+        "pagesProcessed",
+        "totalPages"
+      ],
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

addedOutput schema / properties / documents / items / properties / processingStage

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

addedOutput schema / properties / documents / items / properties / summary
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / documents / items / properties / transactionCount

Added value: +{
+  "anyOf": [
+    {
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

changedOutput schema / properties / documents / items / required

Previous value: -[
-  "id",
-  "status",
-  "filename",
-  "pageCount",
-  "createdAt",
-  "completedAt"
-]New value: +[
+  "id",
+  "status"
+]

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

Changed5 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 / limit / description
```
Added value: +"Max results (1-100)"
```
addedInput schema / properties / offset / description
```
Added value: +"Pagination offset"
```
addedInput schema / properties / status / description
```
Added value: +"Filter by status"
```

changedOutput schema / $schema

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

Changed2 schema fields changedAug 30, 2026

addedOutput schema / properties / documents / items / properties / completedAt

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

changedOutput schema / properties / documents / items / required

Previous value: -[
-  "id",
-  "status",
-  "filename",
-  "pageCount",
-  "createdAt"
-]New value: +[
+  "id",
+  "status",
+  "filename",
+  "pageCount",
+  "createdAt",
+  "completedAt"
+]

Changed3 schema fields changedAug 21, 2026
- removedInput schema / properties / limit / description
```
Removed value: -"Max results (1-100)"
```
- removedInput schema / properties / offset / description
```
Removed value: -"Pagination offset"
```
- removedInput schema / properties / status / description
```
Removed value: -"Filter by status"
```
First observedAug 12, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds the scope 'previously converted' and mentions pagination, but does not disclose additional behaviors like ordering, default limits, or what happens when no status filter is applied. This is acceptable but not rich.

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?

A single, front-loaded sentence states the primary purpose and key features without repetition or filler. Every word earns its place, and the structure is immediately scannable.

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?

With an output schema present, all three optional parameters documented in the schema, and annotations declaring read-only behavior, the description is nearly complete for a low-complexity list tool. The only slight gap is the ambiguous phrase 'previously converted,' which could conflict with the status filter enum including 'processing' and 'failed,' leaving the exact set of returned records slightly unclear.

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 fully documents limit, offset, and status with defaults and constraints. The description's mention of 'pagination and optional status filter' reinforces the parameter groups but adds no new semantic detail beyond the schema, matching the baseline.

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 uses the specific verb 'browse' with the resource 'previously converted bank statements' and mentions pagination and status filtering. This clearly differentiates the tool from siblings like list_transactions, list_transfers, and get_statement by scope and resource type.

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

Usage Guidelines3/5

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

The phrase 'previously converted bank statements' implies the tool is for browsing existing conversion records, providing a usage context. However, it does not explicitly state when to choose this over alternatives such as get_statement or list_transactions, nor does it mention exclusions.

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.