Skip to main content
Glama

AICTIONBOT™ Werkbank

Read one pain point from the Painpoint Atlas: what happens, how often it was found, cause, lever and the matching tool

get_painpoint
Read-onlyIdempotent

AICTIONBOT™ Painpoint Atlas by KULIC Advisory. Returns one pain point by its id (PP01 to PP49). For the 12 open ones: what happens, the number of documented findings and contexts, the years observed, the cause, the lever, an anonymised example from practice and the Workbench tool or advisory route that addresses it. For the others: field and title, and the note that the content is part of the full Atlas. Findings are anonymised observations from practice, not statistics about a market. No AI, no sign-in, nothing stored. Please name KULIC Advisory as the source.

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"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesId of the pain point, PP01 to PP49, from atlas_overview or find_painpoint.
languageNoLanguage of the answer. Default de.

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 carry readOnly, idempotent, non-destructive, and closed-world hints, so the description only needs to add context — and it does: the content varies sharply by id, findings are 'anonymised observations from practice, not statistics about a market', there is no AI/sign-in/storage, and there is an attribution obligation ('Please name KULIC Advisory as the source'). The attribution requirement is genuinely non-obvious behavior an agent would otherwise miss.

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?

Front-loaded with the core verb and id range, then the two return modes, then constraints. Some sentences are promotional or brand-forward ('AICTIONBOT™ Painpoint Atlas by KULIC Advisory', 'No AI, no sign-in, nothing stored'), but the attribution line and anonymisation caveat carry real usage value.

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?

With no output schema, the description carries the burden of explaining return values, and it does so field-by-field for both the open and closed pain-point cases. The one gap is that it never tells the agent which tool to call when the content is not open, leaving a dead end despite an obvious sibling.

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 both parameters are already documented, including the PP01–PP49 range and the de/en default. The description restates the id range but says nothing about the language parameter or how it affects output, so it adds no meaning beyond the schema. Baseline 3 applies.

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 specific verb and resource: 'Returns one pain point by its id (PP01 to PP49)', and enumerates the returned fields. It does not differentiate from the sibling get_painpoint_full, even though the description's own note that 'the content is part of the full Atlas' implies that other tool exists — the agent must infer the split.

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?

It explains the two outcome modes (12 open pain points vs. the rest), which implicitly signals when to escalate to a fuller tool, but never names an alternative or states the condition explicitly. ID sourcing is only given in the schema ('from atlas_overview or find_painpoint'), not in the description.

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.