Skip to main content
Glama

AICTIONBOT™ Werkbank

Prove savings: identified, signed, realised and what actually reached the budget or P&L, with the gaps in euros

track_value
Read-onlyIdempotent

AICTIONBOT™ savings proof by KULIC Advisory, built on the Execution Toolkit template T19 (procurement pipeline and value tracker). Takes the list of savings initiatives with identified, signed (contracted) and realised values and whether the saving reached the budget or P&L (yes, no or an amount), and returns the funnel totals, how many euros of every 100 identified arrive in the budget or P&L, the three gaps (not contracted, signed but not realised, realised but not booked), totals by category and owner, and flags per initiative (realised above contract, marked realised without amount, signed over six months ago with nothing realised, no owner, no baseline). German or English column names are recognised (Maßnahme, Warengruppe, Verantwortlich, Baseline, erkannt, unterschrieben, realisiert, in_budget, Vertragsdatum, Status). 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": {
      "initiatives": "<initiatives>"
    },
    "name": "track_value"
  }
}

Input Schema

NameRequiredDescriptionDefault
as_ofNoReference date, YYYY-MM-DD. Default today.
languageNoLanguage of the answer. Default de.
initiativesYesInitiative rows: initiative, category, owner, baseline, identified, signed, realised, in_budget (yes, no or amount), signed_date, stage.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/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 still adds real behavioural context beyond them: deterministic with no AI, nothing stored, and licence/auth mechanics including the free 30-day check path. It also discloses input flexibility (German or English column names, with the actual aliases listed) and the exact output artefacts, including a maxItems cap of 2000 in the schema.

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 in the second sentence, but that sentence is an extremely long enumeration, and the opening branding line ('AICTIONBOT™ savings proof by KULIC Advisory, built on the Execution Toolkit template T19') carries no operational value for an agent. Dense but not wasteful in substance; the packaging costs it.

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, so the description must carry the return contract, and it does in detail: funnel totals, euros per 100 identified, three named gaps, category and owner totals, and five specific per-initiative flags. Combined with the input row semantics, aliases and auth requirements, an agent has everything needed to call it correctly.

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, but the description earns above that by explaining the semantics of the row fields — in_budget as yes/no/amount — and by listing the accepted German and English column aliases (Maßnahme, Warengruppe, Verantwortlich, Baseline, erkannt, unterschrieben, realisiert, Vertragsdatum, Status). It does not explain as_of or the language default beyond what the schema already says.

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?

After an opening line of branding, the description states a concrete computation: it takes initiatives with identified, signed and realised values plus budget/P&L reach, and returns funnel totals, a per-100-euro conversion, three gap figures, category/owner breakdowns and per-initiative flags. That is specific enough for an agent to recognise the tool. It does not, however, differentiate itself from adjacent analytics siblings such as analyse_spend or build_business_case.

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 describing the required input shape rather than stated as a condition — an agent can infer it is the tool for post-hoc savings proof, but nothing says when to pick it over build_business_case or analyse_spend. The licensing/sign-in note is the only explicit precondition given.

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.