Skip to main content
Glama

AICTIONBOT™ Werkbank

AI and digital readiness: score across eight fields, level, weakest field and the next concrete step

ai_readiness
Read-onlyIdempotent

AICTIONBOT™ AI readiness check by KULIC Advisory, built on the Execution Toolkit templates T28 (AI assessment) and T26 (digital transformation). Takes ratings from 1 (does not apply) to 5 (fully applies) for eight fields: goal, process, data_quality, data_access, ownership, skills, tools, risk. Returns the average, the level (foundations missing, fix the foundation first, pilot possible, ready to scale), the weakest fields and one concrete next step for the weakest. 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": {
      "answers": "<answers>"
    },
    "name": "ai_readiness"
  }
}

Input Schema

NameRequiredDescriptionDefault
answersYesRatings 1 to 5 for goal, process, data_quality, data_access, ownership, skills, tools, risk (at least four).
languageNoLanguage of the answer. Default de.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Beyond readOnlyHint/idempotentHint the description discloses determinism ('no AI'), statelessness ('nothing stored'), and the authentication and quota model: a Werkbank licence is required, otherwise one free check per connection every 30 days via 'Connect without a licence'. Those are behavioural facts an agent cannot recover from the annotations.

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 essential facts (inputs, outputs, licence) come first and every clause carries information. The opening branding and template references (AICTIONBOT™, KULIC Advisory, T28/T26) are the least load-bearing part and add promotional bulk to a single dense paragraph.

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?

No output schema exists, and the description fully enumerates the returned average, level bands, weakest fields and next step, so an agent knows what comes back. The nested-parameter object is documented, but the four-field minimum and partial-answer behaviour are left unaddressed.

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; the description adds genuine meaning by anchoring the scale (1 = does not apply, 5 = fully applies), which the schema only calls 'ratings 1 to 5'. It also lists the field taxonomy that the nested object defines, though it omits the schema's 'at least four' minimum and what happens to missing fields.

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 concrete verb and resource: rates eight named fields (goal, process, data_quality, data_access, ownership, skills, tools, risk) and returns the average, level, weakest fields and one next step. That is enough for an agent to separate it from siblings like check_ai_use_case or assess_team without opening a 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?

Usage is implied by the 'AI readiness check' framing and the licence note makes clear it is a self-contained, licence-gated call. However, there is no explicit when-to-use / when-not-to-use guidance and no routing to an alternative tool for adjacent questions.

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.