Skip to main content
Glama

AICTIONBOT™ Werkbank

Order-to-payment status overview: from one export what is stuck where, per cost centre, with the next step and who has to act

order_to_payment_status
Read-onlyIdempotent

AICTIONBOT™ order-to-payment status overview by KULIC Advisory (tool 66). Takes an export with one row per case (requisition, order number, cost centre, requester, supplier, order value, value received, value invoiced, block, date) and puts every row into one status from its fields: invoice waiting for goods receipt (red), blocked (red), open to order, open to receive, goods receipt without invoice, or done. Returns count and value per status, open cases per cost centre, and the next steps sorted by urgency and age, each with who has to act (purchasing, the requester or accounting) and what to do. Deterministic, no AI, nothing stored. To check a single invoice against order and goods receipt use match_documents. 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

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": {
      "rows": "<rows>"
    },
    "name": "order_to_payment_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
rowsYesOne row per case: requisition, order, cost_center, requester, supplier, value, received, invoiced, blocked (reason or empty), date. German column names work too (anforderung, bestellung, kostenstelle, besteller, lieferant, wert, geliefert, berechnet, gesperrt, datum). A row without an order number counts as not yet ordered.
as_ofNoReference date for the age in days, YYYY-MM-DD. Default today.
languageNoLanguage of the answer. Default de.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description still adds real context: deterministic with no AI, nothing stored, the explicit status taxonomy and colour coding, the ordering logic for next steps, and the licensing gate. It does not say what happens to ambiguous or partially populated rows beyond the no-order-number case, which keeps it from a 5.

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 substance is dense and front-loaded after a short branding clause, and each sentence about statuses, outputs and actors earns its place. The 'AICTIONBOT™ ... (tool 66)' attribution and the lengthy licence sentence are low-value padding that slows the agent down before it reaches the routing hint.

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?

There is no output schema, so the description must explain returns — and it does, specifying per-status counts and values, open cases per cost centre, and next steps sorted by urgency and age with the responsible party. Combined with the input schema and annotations, an agent has everything needed to call it correctly.

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 all three parameters including the as_of date and language enum are already documented in structured data. The description restates the row field list, which largely duplicates the schema, and adds only marginal meaning by implying those fields drive the classification. Baseline 3 is appropriate when the schema carries the parameter burden.

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 names a specific verb and resource — it classifies each row of an order-to-payment export into one status and returns aggregate counts, cost-centre breakdowns and ranked next steps. It explicitly separates itself from match_documents, which handles single-invoice checks, so an agent can distinguish the two without opening either schema.

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

Usage Guidelines5/5

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

It states the input shape required (one row per case export) and names the alternative tool plus the condition that selects it: 'To check a single invoice against order and goods receipt use match_documents.' It also states the access prerequisite and the free-tier limit, so an agent knows when the call will fail rather than how to route it.

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.