Skip to main content
Glama

AICTIONBOT™ Werkbank

Handover file when someone leaves or goes on holiday: open approvals, contracts, deadlines, orders, invoices and contacts with a deputy per item

build_handover_file
Read-onlyIdempotent

AICTIONBOT™ handover file by KULIC Advisory (tool 41), built on the Execution Toolkit template T07 (cross-functional action log). Takes the person, the deputy, the absence (away_from, away_to; empty away_to means the person leaves, the first 90 days are covered) and a list of open items (type: approval, contract or deadline, order, invoice, supplier, task; item; due date; value; supplier; deputy; status; note). Returns what must be settled before the last day (approvals tied to the person, deadlines in the absence, overdue items, items without a deputy, in red), what falls due during the absence, later items, contacts, the load per deputy, a five-point handover meeting and the hand-back date. 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": {
      "person": "<person>",
      "items": "<items>"
    },
    "name": "build_handover_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
as_ofNoReference date, YYYY-MM-DD. Default today.
itemsYesOpen items: type, item, due, value, supplier, deputy, status, note. German column names work too.
deputyNoDeputy or successor for all items without their own.
personYesWho is leaving or away.
away_toNoLast day of absence. Leave empty if the person leaves for good.
languageNoLanguage of the answer. Default de.
away_fromNoFirst day of absence, YYYY-MM-DD or DD.MM.YYYY. Default today.

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 adds genuinely useful context beyond that: 'Deterministic, no AI, nothing stored', a licence requirement, and the free-tier limit of one check per connection every 30 days. The remaining gap is the 90-day coverage window, which is mentioned but not explained.

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?

It is a single dense block whose opening clause is vendor branding and template lineage rather than the function, so the purpose is not front-loaded. The content is substantive and free of filler once it starts, but the run-on structure and marketing prefix make it harder to scan than necessary.

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 seven-parameter tool with no output schema, the description compensates well by spelling out the returned sections (red-flagged items, due-during-absence items, contacts, deputy load, handover meeting, hand-back date). With schema coverage at 100% and annotations covering safety, an agent has what it needs to invoke the tool correctly; only the licence/free-tier boundary could be sharper.

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 seven parameters including as_of, away_from, language and the items array are already documented. The description largely restates those semantics (person, deputy, away_from/away_to, item types) and adds only marginal value such as the enumeration of item types and the 'first 90 days' note. Baseline 3 is appropriate where the schema carries the load.

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 concrete verb and artifact ('handover file') and enumerates exactly what it ingests (person, deputy, absence window, open items) and what it returns (what must be settled before the last day, items due during absence, contacts, deputy load, handover meeting, hand-back date). It is clearly distinguishable from siblings like check_contracts or open_table by domain. It loses a point only because the actual purpose is buried behind branding ('AICTIONBOT™ ... tool 41 ... template T07').

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?

The usage situation is implied by the title ('when someone leaves or goes on holiday') and by the semantics of away_to ('empty away_to means the person leaves'), so an agent can infer when to reach for it. However, the description never explicitly says when to use this instead of alternatives such as check_actions or audit_list, and gives no exclusions or prerequisites beyond the licence note.

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.