Skip to main content
Glama

AICTIONBOT™ Werkbank

Statement reconciliation: a supplier's statement against your own open items and payments, with paid, open, blocked, unknown and duplicate documents and the reply letter

reconcile_supplier_statement
Read-onlyIdempotent

AICTIONBOT™ statement reconciliation by KULIC Advisory (tool 53). Takes the supplier's statement of account (documents with amount) and your own items for that supplier (document, amount, status open, paid or blocked, payment date, block reason) and matches them by document number, tolerant of prefixes, spaces and leading zeros. Returns per supplier document: paid with the payment date, open with due date and days overdue, blocked with the reason, unknown on your side, listed twice on the statement, amount differs; plus items booked on your side that the statement does not show, such as credit notes not deducted. Totals show what the supplier claims and how much of it is paid, open, blocked, unknown or duplicated. Ends with a ready reply letter to the supplier. Pass two arrays (statement, ledger) or one array rows with a side column (Supplier or We). Deterministic, no AI, nothing stored. Needs sign-in: runs with an AICTIONBOT™ Werkbank licence; without a licence one check per connection every 30 days is free (sign in with “Connect without a licence”).

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": "reconcile_supplier_statement"
  }
}

Input Schema

NameRequiredDescriptionDefault
rowsNoAlternative to statement and ledger: one list with a side column (Supplier or We; German: Lieferant or Wir) plus the columns above.
as_ofNoReference date, YYYY-MM-DD. Default today.
ledgerNoYour own rows for this supplier: document, date, amount (negative for credit notes), status (open, paid, blocked), paid_on, block_reason, due.
languageNoLanguage of the answer. Default de.
supplierNoSupplier name for the heading.
statementNoSupplier statement rows: document, date, amount, due (optional). German column names work too.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the readOnly/idempotent/non-destructive annotations, the description discloses determinism ('no AI'), that nothing is stored, and an operational precondition the annotations cannot express: sign-in and licensing, with the exact 30-day free check per connection. It also enumerates the outcome classes the agent will receive, so behavior is predictable before calling.

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?

Front-loaded with purpose, then outputs, then input modes, then licensing — a sound order where each block earns its place. Minor waste remains in the branding string 'AICTIONBOT™ statement reconciliation by KULIC Advisory (tool 53)' and a long output enumeration that could be tightened.

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 no output schema, the description carries the full burden of explaining returns and does so concretely: per-document statuses with dates, overdue days, reasons, totals, and a closing reply letter. For a six-parameter, zero-required tool with alternative input shapes, the modes and licensing caveats are all covered.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning the schema cannot: statement and ledger versus a single rows array with a Supplier/We side column are mutually exclusive input shapes, and it clarifies that credit notes appear as negative amounts and that German column names are accepted. The document-number tolerance note is genuine semantic value for the item-level fields.

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 opens with a specific verb and resource ('statement reconciliation') and immediately defines the two input sets and the matching key (document number, tolerant of prefixes/spaces/leading zeros), so the operation is unmistakable. It never names a sibling such as match_documents or check_invoice to say what it is not, so it stops short of full sibling differentiation.

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 implied by the input description: reconcile when you hold a supplier statement of account alongside your own open/paid/blocked items. The either/or input modes are spelled out, but there is no explicit when-not guidance and no routing to related tools like match_documents or check_invoice_payment.

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.