Skip to main content
Glama

get_bank_status

Composed bank snapshot — "is my banking up to date?" (CompanyMember). "Reconciled" means entries matched, NOT ledger = statement balance (the close check BANK_BALANCE_DOES_NOT_TIE_OUT compares that).

Per-account entry-status and in_suspense counts, each account's latest closing balance, and the company-level cumulative GL Suspense balance. Non-zero suspense blocks a clean VAT close.

Read-only. Gaps come from the account's full history: coverage windows are merged and every internal hole reported (ZCT-509), so a run of missing statements is ONE gap. Not period-scoped; use …/reconciliation/completeness per month. period_gaps caps at 10/account, period_gap_count stays exact — HOLES, not missing months. Explicit non-member company_id → 403.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "company_id": "<company_id>"
    },
    "name": "get_bank_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
company_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

With no annotations present, the description carries the full load and does so well: it declares read-only access, the 403 behavior for a non-member company_id, the CompanyMember scope, and the truncation rule (period_gaps capped at 10/account while period_gap_count stays exact). It also warns that gaps come from full history with merged windows, so a run of missing statements reads as one gap — behavior an agent could not infer otherwise.

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?

The purpose sentence is front-loaded and each subsequent block carries real information (semantics of 'Reconciled', suspense implications for VAT close, gap semantics, caps). It is dense but slightly cluttered by internal references (ZCT-509, BANK_BALANCE_DOES_NOT_TIE_OUT) that add length without much agent-facing value.

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 read-only snapshot tool with no output schema, the description conveys what comes back at a useful level (entry-status, suspense counts, closing balances, cumulative suspense) and flags the VAT-close implication of non-zero suspense. Minor gaps remain: the enumeration of entry-status values and whether the response is per-account only or includes totals are not spelled out.

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?

The single company_id parameter has zero schema description coverage, so the description must compensate. It does add one meaningful constraint — an explicit non-member company_id yields 403 — but never states the identifier's format or how to discover a valid one (e.g., via list_companies).

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 concrete verb+resource ('Composed bank snapshot') and enumerates the payload: per-account entry-status and in_suspense counts, latest closing balance, and company-level cumulative GL Suspense balance. It also pre-empts a likely misreading by defining what 'Reconciled' does NOT mean, which separates it from balance/tie-out tools like gl_trial_balance.

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?

Frames the tool around a concrete question ('is my banking up to date?') and explicitly routes period-scoped questions elsewhere ('Not period-scoped; use …/reconciliation/completeness per month'). That alternative is a REST path rather than a listed sibling tool, so the routing is slightly less actionable than a direct tool-to-tool handoff.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources