Skip to main content
Glama

Bankstatemently

by io.github.bankstatemently
OverviewDiscussionsAdmin

Get Credit Balance

get_credits
Read-only

Your remaining Bankstatemently credits — the processing quota, NOT credit/debit transactions. Use for: how many credits do I have, remaining pages, plan limits, quota, how many pages can I upload. 1 credit = 1 page of bank statement processing. Also reports your plan's operational limits (max pages per upload, max upload size, daily spend cap) so you can size a multi-file batch correctly before starting it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
planYes
limitYes
planIdYes
balanceYes
grantedYes
summaryYes
creditsExpireAtYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / plan / properties / memoriesCap
      Added value: +{
+  "anyOf": [
+    {
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}
    • changedOutput schema / properties / plan / required
      Previous value: -[
-  "maxPagesPerUpload",
-  "maxUploadSizeMb",
-  "dailySpendCap",
-  "monthlyPages"
-]New value: +[
+  "maxPagesPerUpload",
+  "maxUploadSizeMb",
+  "dailySpendCap",
+  "monthlyPages",
+  "memoriesCap"
+]
  2. Changed1 schema field changed
    • changedOutput schema / properties / planId / anyOf
      Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "enum": [
+      "anonymous",
+      "free",
+      "credit_pack",
+      "beginner",
+      "pro",
+      "enterprise"
+    ],
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
  3. Changed4 schema fields changed
    • addedOutput schema / properties / granted
      Added value: +{
+  "type": "number"
+}
    • addedOutput schema / properties / plan / properties / monthlyPages
      Added value: +{
+  "anyOf": [
+    {
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}
    • changedOutput schema / properties / plan / required
      Previous value: -[
-  "maxPagesPerUpload",
-  "maxUploadSizeMb",
-  "dailySpendCap"
-]New value: +[
+  "maxPagesPerUpload",
+  "maxUploadSizeMb",
+  "dailySpendCap",
+  "monthlyPages"
+]
    • changedOutput schema / required
      Previous value: -[
-  "balance",
-  "limit",
-  "planId",
-  "creditsExpireAt",
-  "plan",
-  "summary"
-]New value: +[
+  "balance",
+  "limit",
+  "granted",
+  "planId",
+  "creditsExpireAt",
+  "plan",
+  "summary"
+]
  4. Changed2 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"
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  5. Changed2 schema fields changed
    • addedOutput schema / properties / plan
      Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "dailySpendCap": {
+      "anyOf": [
+        {
+          "type": "number"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "maxPagesPerUpload": {
+      "type": "number"
+    },
+    "maxUploadSizeMb": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "maxPagesPerUpload",
+    "maxUploadSizeMb",
+    "dailySpendCap"
+  ],
+  "type": "object"
+}
    • changedOutput schema / required
      Previous value: -[
-  "balance",
-  "limit",
-  "planId",
-  "creditsExpireAt",
-  "summary"
-]New value: +[
+  "balance",
+  "limit",
+  "planId",
+  "creditsExpireAt",
+  "plan",
+  "summary"
+]
  6. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already establish read-only/non-destructive. The description adds value beyond them: the quota unit ('1 credit = 1 page'), and the fact that plan operational limits (max pages per upload, max upload size, daily spend cap) are returned, which tells the agent this call is useful before batching.

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?

Front-loaded with the core meaning and the disambiguation first, then the use cases, then the quota unit and returned limits. Every sentence earns its place; the trigger-query list is compact rather than padded.

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?

With an output schema present, the description need not detail return fields, and it correctly summarizes what comes back (quota plus plan limits). For a zero-parameter, read-only tool this is complete.

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?

Zero parameters, so there is no argument semantics to explain; baseline 4 applies. The description correctly avoids inventing parameter details that do not exist.

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?

Specific verb+resource ('remaining Bankstatemently credits') immediately disambiguated from the common false reading ('NOT credit/debit transactions'). An agent cannot confuse this with transaction-listing siblings 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 Guidelines4/5

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

Explicitly enumerates trigger queries ('how many credits do I have, remaining pages, plan limits, quota, how many pages can I upload') and the pre-batch sizing use case. It clarifies conditions for use, but does not name a competing sibling tool or an explicit when-not-to-use.

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

Resources