Skip to main content
Glama

AICTIONBOT™ Werkbank

Blanket order guard: remaining budget, monthly use, the day the budget runs out and invoices without cover

check_blanket_orders
Read-onlyIdempotent

AICTIONBOT™ blanket order guard by KULIC Advisory (tool 55). Takes blanket or limit purchase orders (order, value, called off so far, start, end; optional supplier and open invoices not yet booked). Returns per order the remaining budget, the share used, the use per month, the day the budget is expected to run out compared with the end of the term, invoices that are not covered, a traffic light and the next step (top up, renegotiate, framework contract instead of an order, follow-up order). 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_blanket_orders"
  }
}

Input Schema

NameRequiredDescriptionDefault
rowsYesBlanket orders: order, supplier, value, called_off, open_invoices, start, end. German column names work too (Bestellung, Wert, Abgerufen, Offene Rechnungen, Beginn, Ende).
as_ofNoReference date, YYYY-MM-DD. Default today.
languageNoLanguage of the answer. Default de.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/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 adds genuinely new context: deterministic with no AI, nothing stored, sign-in required under a Werkbank licence, and a free tier of one check per connection every 30 days. That licence/rate-limit disclosure is exactly the kind of operational constraint 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.

Conciseness4/5

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

The output contents are front-loaded in one dense sentence followed by operating constraints, with little redundancy. The 'AICTIONBOT™ ... by KULIC Advisory (tool 55)' branding prefix is promotional overhead that does not help tool selection.

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?

There is no output schema, and the description fully enumerates the returned metrics and the recommended next steps (top up, renegotiate, framework contract, follow-up order). Combined with the licence requirement and the 3000-row input cap in the schema, an agent has everything needed to call it and interpret the result.

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 applies; the description restates the field set (order, value, called off so far, start, end, supplier, open invoices) which the schema already documents, including the German column aliases. The only added nuance is that open_invoices means invoices not yet booked, and as_of/language are not mentioned at all.

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: takes blanket/limit purchase orders and returns remaining budget, share used, monthly consumption, projected exhaustion date vs. term end, uncovered invoices, traffic light and next step. This is unmistakably distinct from siblings like check_invoice, check_contracts or check_expenses, which operate on different objects.

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?

The description clearly delimits the applicable input domain (blanket or limit purchase orders with value, called-off amount, start/end, optional supplier and unbooked invoices), which tells the agent when this tool fits. It does not name an alternative tool or state exclusions, so routing must still be inferred from the input shape.

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.