Skip to main content
Glama

AICTIONBOT™ Werkbank

Weekly status as a traffic light: each figure against last week and target, what moved most

weekly_status
Read-onlyIdempotent

AICTIONBOT™ weekly status by KULIC Advisory, built on the Execution Toolkit template T01 (CEO dashboard). Takes the week's figures with last week's value and an optional target, or a table of weekly values (one row per week) with targets, and rates each figure by the template rule: above plus 5 percent against last week green, down to minus 5 percent amber, below that red (reversed for figures where lower is better, such as overdue receivables or complaints; the threshold can be changed). Returns the status per figure, the gap to target, the three biggest movers and a question for each red figure. 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

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "weekly_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
weeksNoAlternative: one row per week, one column per figure; the last two rows are compared.
metricsNoRows: metric, current, previous, target, better (higher or lower), note.
targetsNoTargets per figure name, for weeks.
languageNoLanguage of the answer. Default de.
threshold_percentNoChange against last week that counts as green or red. Default 5.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior, and the description adds real context beyond them: deterministic with no AI, nothing stored, the lower-is-better reversal for figures like overdue receivables, an adjustable threshold, and a licensing gate with a free 30-day single-check path via 'Connect without a licence'. That auth/licensing and reversal behavior is exactly the kind of disclosure annotations cannot carry. It stops short of describing the response shape in detail, but the key behavioral traits are covered.

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 content is dense and mostly front-loaded, but the opening branding clause ('AICTIONBOT™ weekly status by KULIC Advisory, built on the Execution Toolkit template T01 (CEO dashboard)') is marketing padding that does not help an agent invoke the tool. Everything is also compressed into one long paragraph, so the input modes, the rating rule, the outputs, and the licensing terms are hard to scan apart.

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?

There is no output schema, so the description must carry the return values, and it does: status per figure, gap to target, three biggest movers, and one question per red figure. For a five-parameter, zero-required tool with nested objects, the remaining gap is minor — it does not clarify behavior when a target is omitted or when fewer than two weeks are supplied.

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, and the description earns an extra point by explaining semantics the schema only hints at: the threshold is the change against last week that counts as green or red, the lower-is-better flag is what triggers the reversal, and targets apply to the weeks mode. It still leaves the exact nested row fields (metric/current/previous/target/better/note) to the schema, which is appropriate.

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?

States a concrete verb and resource: it takes weekly figures (or a table of weekly values) and rates each one as green/amber/red by the T01 template rule. The transformation and the outputs (status per figure, gap to target, top three movers, a question per red figure) are explicit, so the tool is easy to recognize. It does not name or contrast any sibling tool (e.g. check_kpis), so differentiation is left to inference.

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 two accepted input shapes — either current/previous/target per metric, or one row per week with targets — which tells an agent which situations fit. There is no explicit when-to-use vs. when-not guidance, no statement about which of the two input modes to prefer, and no routing to alternative tools for adjacent needs.

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.