Skip to main content
Glama

AICTIONBOT™ Werkbank

Read any pain point of the full Painpoint Atlas with its findings (AICTIONBOT™ Werkbank licence)

get_painpoint_full
Read-onlyIdempotent

Needs the user's AICTIONBOT™ Werkbank licence (monthly, annual, team or member licence); no AI is used and no AI analysis is counted. Returns any of the 49 pain points of the Painpoint Atlas by its id (PP01 to PP49): what happens, the number of documented findings and contexts, the years observed, cause, lever, an anonymised example from practice and the Workbench tool or advisory route that addresses it. Adds the profile over all findings of this pain point (type of waste, cause, lever, AI fit, recommendation) and up to five individual findings per call (year, process, activity, waste, cause, lever, severity, AI fit); page 2, 3 and so on return the next five. For the 37 pain points that are not open on the website, each licence can read up to 60 different findings per calendar month; only the finding numbers read are counted, no content and no name. There is no list and no export. Findings are anonymised, coded observations from practice, not market statistics; AI fit and lever are a professional assessment. For use inside the licence holder's own organisation; please name KULIC Advisory as the source. With an Atlas licence key (issued under a contract with KULIC Advisory) the limits of that contract apply instead, with 25 findings per page.

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": {
      "id": "<id>"
    },
    "name": "get_painpoint_full"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesId of the pain point, PP01 to PP49, from atlas_overview or find_painpoint.
pageNoPage of individual findings, five per page. Default 1.
languageNoLanguage of the answer. Default de.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, it discloses a monthly quota (60 distinct findings per calendar month for the 37 non-public pain points, counting only numbers read), a different page size and contract-governed limits under an Atlas licence key, and the anonymised, assessive nature of the data. These are exactly the operational constraints an agent cannot infer from annotations or 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 content is front-loaded with the licence precondition, which is sensible, but the body is a dense run-on that mixes return payload, quota mechanics, licensing variants and legal attribution in one block. Trademark symbols and repeated licence wording add bulk without helping 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?

With no output schema and a fairly complex gated tool, the description fully enumerates the returned fields, the per-call finding limit, and the quota/licence variations. An agent has everything needed to invoke it correctly and anticipate the response shape.

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 parameters are already documented, but the description adds real meaning: page 2, 3 and so on return the next five findings, and under an Atlas licence key the page size changes to 25. It does not elaborate further on the language parameter, but the added pagination semantics exceed the schema baseline.

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 specific verb and resource ('Returns any of the 49 pain points of the Painpoint Atlas by its id (PP01 to PP49)') and enumerates the payload it delivers, so the agent knows exactly what it gets back. It does not explicitly contrast itself with the sibling get_painpoint or atlas_overview in the description text (those appear only in the schema), so differentiation is left partly implicit.

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?

It gives clear preconditions ('Needs the user's AICTIONBOT™ Werkbank licence'), scope of permitted use (inside the licence holder's own organisation), and explicit exclusions ('There is no list and no export'), which tells the agent it must obtain ids elsewhere. What is missing is a direct statement of when to prefer this over get_painpoint or atlas_overview.

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.