Skip to main content
Glama

Bank reconciliation status

accounting_reconciliation_status
Read-onlyIdempotent

Bank reconciliation status per uploaded statement, plus the bank payments that still need a slip or invoice. Read-only. Needs the user's GetAccountED sign-in (they are asked to sign in the first time).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "accounting_reconciliation_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
business_idNoAccounting practices only: which client's books (an id from accounting_list_my_businesses). Leave out to use the books chosen at sign-in.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely non-structured context: results are per uploaded statement, and the call requires the user's GetAccountED sign-in with a first-time sign-in prompt, which tells the agent to expect an auth interruption. It stops short of describing result shape or size, but no output schema exists to defer to.

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?

Three short sentences, front-loaded with what is returned, followed by the read-only guarantee and the auth requirement. No filler or redundant restatement of the title.

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 zero-required-parameter read tool with no output schema, the description covers scope, safety, and the auth prerequisite an agent must anticipate. The one gap is that the shape of 'status per statement' (counts, matched/unmatched lines, per-account grouping) is left entirely unspecified.

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%, and the single optional business_id is fully documented in the schema including its default behavior at sign-in and its link to accounting_list_my_businesses. The description adds no parameter-level meaning beyond that, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource and scope: 'Bank reconciliation status per uploaded statement' plus 'the bank payments that still need a slip or invoice'. That is concrete enough for an agent to know this is a reconciliation/outstanding-documentation report rather than a generic ledger or listing tool. It doesn't explicitly contrast itself with the closely related sibling accounting_unfiled_bank_lines, which keeps it from a 5.

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?

Usage is only implied: the agent can infer it is for checking how far a bank statement has been reconciled and which payments lack supporting documents. There is no statement of when to prefer it over accounting_unfiled_bank_lines, accounting_general_ledger, or accounting_overview, and no exclusions or prerequisites beyond the sign-in note.

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.