Skip to main content
Glama

AICTIONBOT™ Werkbank

Check a supplier's new price list against the old one before loading it: increases per item, hidden unit changes, new and dropped items

check_catalog
Read-onlyIdempotent

AICTIONBOT™ Catalog Checker by KULIC Advisory. Puts a supplier's new price list (catalog) next to the old one and returns what needs attention before it is loaded: increases per item against a threshold, hidden changes in unit, price unit or content, new and dropped items, duplicates, implausible prices, invalid EANs, and the weighted change and extra cost per year when annual quantities are given. Without an old list it checks the new list on its own. 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

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": {
      "new_list": "<new_list>"
    },
    "name": "check_catalog"
  }
}

Input Schema

NameRequiredDescriptionDefault
languageNoLanguage of the answer. Default de.
new_listYesNew price list rows: article_no, description, price, unit, price_unit (price per how many units, default 1), content (e.g. sheets per pack), min_order, ean, currency.
old_listNoOptional old price list in the same form, plus annual_quantity (per year, in sales units of the old list) to weight the change.
threshold_percentNoIncrease per item that needs a look, in percent. Default 5. Three times the threshold is a stop.

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?

Annotations already declare readOnly, idempotent, non-destructive and closed-world, and the description still adds substantial context beyond them: deterministic with no AI, nothing stored, licence requirement, and a concrete free-tier limit of one check per connection every 30 days including how to sign in. These are exactly the operational constraints annotations cannot convey.

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?

All information is packed in a single dense paragraph led by branding ('AICTIONBOT™ Catalog Checker by KULIC Advisory') rather than the core action. The licensing and free-tier sentences, while useful, are lengthy, and the check list is a long comma run that is harder to scan than it needs to be.

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?

With no output schema, the description carries the burden of describing results, and it does so by enumerating the categories of findings returned plus the weighted annual figures. What it does not describe is the response shape (per-item rows vs. a summary, how stop-level increases are flagged), which leaves a small gap for a tool returning this much analysis.

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. The description still adds meaning: threshold_percent semantics ('increases per item against a threshold', with three times the threshold being a stop) and the fact that annual_quantity on the old list drives a weighted change and extra cost per year, which explains why passing the old list matters.

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 verb and resource: comparing a supplier's new price list against the old one and returning discrepancies. It covers what is checked in detail (price increases against a threshold, unit/content changes, new/dropped items, duplicates, invalid EANs, weighted annual impact). It does not explicitly differentiate from sibling tools such as check_price_increase or rate_supplier, 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 Guidelines4/5

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

It clearly states the usage context ('before it is loaded') and a key branch: 'Without an old list it checks the new list on its own.' It does not name alternative tools or say when a sibling (e.g. check_price_increase) would be the better choice, so it stops short of full routing guidance.

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.