Skip to main content
Glama

AICTIONBOT™ Werkbank

Issue radar: recurring causes in a list of procurement or invoice problems, age, open cases per owner and the fix for each cause

analyse_issues
Read-onlyIdempotent

AICTIONBOT™ issue radar by KULIC Advisory (tool 43), built on the Execution Toolkit templates T05 (process improvement) and T07 (action log). Takes a list of cases or tickets (case, date, description, optional cause, owner, status, supplier) and groups them into ten recurring causes by keywords (invoice without purchase order, price difference, quantity or goods receipt, master data, approval stuck, payment or reminder, late delivery, quality or complaint, duplicate invoice, invoice details or tax). A cause column takes priority. Returns the five most frequent causes with share, open cases and the fix with the matching Workbench tool, typical age, cases older than 30 days, open cases per owner and suppliers with three or more cases. 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": {
      "issues": "<issues>"
    },
    "name": "analyse_issues"
  }
}

Input Schema

NameRequiredDescriptionDefault
as_ofNoReference date, YYYY-MM-DD. Default today.
issuesYesRows: case, date, description, cause (optional), owner, status (open or done), supplier. German column names work too.
languageNoLanguage of the answer. Default de.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/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 value beyond them: deterministic with no AI, nothing stored, and an explicit licensing/auth requirement including the free once-per-30-days check without a licence. What it does not disclose is failure behavior on invalid rows or what happens above the 5,000-row cap.

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 operational content is dense and informative, but the opening clause — brand name, 'tool 43', and template codes T05/T07 — is pure provenance that does not help an agent decide or invoke. The ten-cause enumeration is long yet earns its place because it defines the grouping behavior. Front-loading the branding ahead of the purpose is a structural weakness.

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?

For a read-only analytical tool with a fully documented three-parameter schema and no output schema, the description carries the return contract well: top five causes, shares, open counts, fixes, age, stale cases and supplier thresholds. Minor gaps remain around validation of malformed rows and the behavior of as_of when cases fall outside the window.

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 — issues, as_of, language — are already documented in the schema, including defaults and the German column-name tolerance. The description adds one genuinely useful semantic point, that an existing cause column takes priority over keyword grouping, but it says nothing further about as_of or the language switch, so baseline 3 applies.

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 states a specific verb and resource: it takes a list of cases/tickets and groups them into ten recurring causes, then returns the top five with share, open cases, fixes, age, owner breakdown and supplier flags. The scope is unusually concrete. It does not name a sibling tool to contrast with (find_in_list, audit_list, check_invoice are plausible confusions), so it stops short of 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 Guidelines3/5

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

Usage is implied by the input shape — a list of procurement or invoice cases in which a cause column can override keyword grouping. There is no explicit when-to-use versus when-not guidance, and no named alternative for a single-case check (e.g. check_invoice) or a raw list lookup, leaving the agent to infer selection from the domain wording.

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.