Skip to main content
Glama

AICTIONBOT™ Werkbank

Supplier error profile: which supplier makes which errors in a list of clarification cases, what clearing them up costs, a ready letter per supplier

supplier_error_profile
Read-onlyIdempotent

AICTIONBOT™ supplier error profile by KULIC Advisory (tool 65). Takes a list of clarification cases or rejected invoices and deliveries (supplier, error text, optionally minutes spent) and sorts every case into nine error types by keywords (order number missing or wrong, delivery note, invoice sent twice, price, quantity, late delivery, faulty or wrong goods, mandatory invoice details, bank details or address not reported). Returns the most frequent errors, the five suppliers with the most cases with hours and cost of clarification, the share of the top three, and a ready letter per supplier with three or more cases naming their three most frequent errors and the request for each. The cost uses your hourly rate and minutes per case; without them it assumes 45 euros per hour and 20 minutes per case and says so. Deterministic, no AI, nothing stored. For causes inside your own process use analyse_issues. 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": "supplier_error_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
rowsYesOne row per case: supplier, error (free text), optionally minutes. German column names work too (lieferant, fehler, minuten).
languageNoLanguage of the answer. Default de.
hourly_rate_eurNoOptional: internal cost per hour in euros. Default 45.
minutes_per_caseNoOptional: minutes per case where the row gives none. Default 20.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, closed-world, non-destructive behavior, and the description still adds real value: deterministic keyword classification with no AI, nothing stored, and an explicit statement that the 45 EUR/20 min defaults are disclosed in the answer when not supplied. Auth requirements and the licence/free-check fallback are also spelled out, which annotations never cover.

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 behavior is front-loaded in the first two sentences, but the paragraph is dense and carries filler: the 'AICTIONBOT™ ... by KULIC Advisory (tool 65)' branding and a repeated restatement of the hourly-rate/minute defaults already documented in the schema. The licence and free-check sentence is long but genuinely load-bearing, so the main waste is branding rather than substance.

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 return-value burden and does it: nine error types enumerated, top-five supplier table with hours and cost, top-three share, and the letter generation rule (three or more cases, three most frequent errors plus the request per error). Prerequisites, cost assumptions, and the 'nothing stored' guarantee round out what an agent needs to call it and interpret results.

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 goes beyond it by explaining that the 'error' free text is keyword-sorted into nine specific error types, which tells the caller what kind of text to put in rows. It also restates the cost defaults, which overlaps with the schema rather than extending it, keeping it below a 5.

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 chain: it takes clarification cases or rejected invoices/deliveries, classifies them into nine named error types, and returns frequencies, top-five suppliers with hours/cost, top-three share, and a per-supplier letter. The final sentence names the sibling it is not ('For causes inside your own process use analyse_issues'), so an agent can separate it from alternatives without opening a schema.

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 usage context (supplier-attributable errors in clarification cases) and an explicit exclusion routing internal-process causes to analyse_issues. It also states the access precondition (Werkbank licence, or a 30-day free single check). It stops short of spelling out when the output is unsuitable, e.g. small case lists that won't reach the three-case letter threshold.

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.