Skip to main content
Glama

AICTIONBOT™ Werkbank

Approval backlog radar: who is holding which invoice or order, how long, which discounts are at risk, and whom to reroute to

check_approval_backlog
Read-onlyIdempotent

AICTIONBOT™ approval backlog radar by KULIC Advisory (tool 54). Takes the list of open approvals (document, amount, approver, waiting since; optional supplier, due date, discount date and percent, approver away until, deputy). Returns the backlog per approver with number, amount and oldest age in days, flags documents red or yellow (overdue, discount expiring, waiting longer than the limit, approver away), sums the cash discount at risk, proposes remind or reroute to the deputy per person and writes a ready reminder to the person with the most urgent backlog. 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": {
      "rows": "<rows>"
    },
    "name": "check_approval_backlog"
  }
}

Input Schema

NameRequiredDescriptionDefault
rowsYesOpen approvals: document, supplier, amount, approver, since (date), due, discount_until, discount (percent), absent_until, deputy. German column names work too (Beleg, Betrag, Freigeber, Seit, Fällig, Skonto bis, Abwesend bis, Vertretung).
as_ofNoReference date, YYYY-MM-DD. Default today.
languageNoLanguage of the answer. Default de.
limit_daysNoDays a document may wait before it turns yellow; twice that turns it red. Default 5.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/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 adds genuinely useful context beyond that: deterministic with no AI, nothing stored, and the sign-in/licence requirement with a free 30-day check. It stops short of describing output format or the reminder-writing side effect in detail.

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 content is front-loaded and dense, but the opening brand boilerplate ('AICTIONBOT™ ... by KULIC Advisory (tool 54)') and the trailing licence paragraph consume space without helping an agent invoke the tool. The single run-on sentence is harder to parse than a structured list would 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 explaining returns, and it does so well: per-approver counts, amounts, oldest age, red/yellow flags, discount at risk, and per-person remind/reroute proposals. Only the exact response shape and the reminder-writing side effect remain underspecified.

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 four parameters are already documented, including the red/yellow threshold rule for limit_days and the German column aliases. The description restates the input fields and the red/yellow logic but adds no syntax or format detail beyond the schema, so the baseline 3 applies.

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 ('approval backlog radar') and enumerates the concrete operations: aggregates backlog per approver, flags red/yellow, sums discount at risk, proposes remind or reroute, and writes a reminder. An agent can tell exactly what this tool produces without opening the schema.

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?

It implies the input context (a list of open approvals) and states the licence/free-tier condition, but gives no explicit when-to-use versus when-not guidance and names no alternative sibling such as check_discount_window or check_approval_matrix. Usage is inferable but not directed.

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.