Skip to main content
Glama

AICTIONBOT™ Werkbank

Quantity and unit check: ordered against received quantity per line with the cause (over-delivery, lot size, different unit, under-delivery), the amount and the fix

check_quantities
Read-onlyIdempotent

AICTIONBOT™ quantity and unit check by KULIC Advisory (tool 71). Takes order and goods receipt lines (order, item, ordered quantity and unit, received quantity and unit, unit price, optional lot size) and names the cause of every deviation from its fields: a different unit of measure with the probable conversion factor (red), over-delivery beyond the tolerance (red), a quantity rounded up to the lot size (yellow) or under-delivery (yellow), each with the amount where a price is given and the fix (tolerance, master data, return, chase the rest). Tolerance in percent, default 5. Deterministic, no AI, nothing stored. To match an invoice with 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": "check_quantities"
  }
}

Input Schema

NameRequiredDescriptionDefault
rowsYesOne row per line: order, item, ordered, unit_ordered, received, unit_received, price, lot_size. German column names work too (bestellung, artikel, bestellt, einheit_bestellt, geliefert, einheit_geliefert, preis, losgroesse).
languageNoLanguage of the answer. Default de.
tolerance_percentNoOptional: tolerance in percent. Default 5.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/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 bar is lower. The description still adds real behavioral context beyond them: deterministic with no AI, nothing stored, licence requirement with a free one-check-per-30-days fallback, and the red/yellow severity coding of findings.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core explanation is front-loaded and dense, but vendor boilerplate ("AICTIONBOT™ ... by KULIC Advisory (tool 71)"), the repeated brand in the licence sentence, and the inline licence/free-tier paragraph add length that does not help tool selection or invocation.

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 burden of describing results and does so: deviation categories with color severity, the amount, and the suggested fix per case. Combined with the input shape and licence prerequisites, an agent has everything needed to call it and interpret the answer.

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 the baseline is 3. The description only reinforces what the schema already says (tolerance default 5, optional lot size and price) and clarifies that an amount is reported only where a price is supplied — modest added meaning rather than new syntax or constraints.

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 specific verb and resource — comparing order lines against goods receipt lines on quantity and unit — and enumerates exactly what it outputs (deviation cause, amount, fix). It also names the sibling match_documents as the different tool for invoice matching, so the agent can separate the two without opening schemas.

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?

Gives a clear selection rule for the adjacent task ("To match an invoice with order and goods receipt use match_documents") and states the input shape needed to invoke it. It does not explicitly exclude other check_* siblings or say when a quantity check is unnecessary, so guidance is strong but not exhaustive.

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.