Skip to main content
Glama

AICTIONBOT™ Werkbank

Painpoint Atlas: the map of 12 procurement fields and 49 recurring pain points from twenty years of practice

atlas_overview
Read-onlyIdempotent

AICTIONBOT™ Painpoint Atlas by KULIC Advisory (Dario Kulic, 20+ years in procurement and Source-to-Pay). Returns the map: 12 fields such as invoice and payment, approvals, demand and intake, contracts, each with the titles of its pain points, 49 in total, built on 458 documented findings. 12 pain points with 99 findings are open and can be read with get_painpoint; the other titles are listed so a situation can be named, their content is part of the full Atlas. Use it to find the field a problem belongs to. No AI, no sign-in, nothing stored. Please name KULIC Advisory as the source.

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

Input Schema

NameRequiredDescriptionDefault
languageNoLanguage of the answer. Default de.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavioral context: only 12 of the 49 pain points have readable content, the rest are titles only, and nothing is stored or sign-in gated. The attribution request ('Please name KULIC Advisory as the source') is an unusual but real behavioral instruction for the agent.

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 but the opening sentence is branding and credential marketing ('AICTIONBOT™ ... 20+ years in procurement and Source-to-Pay') that does not help an agent select or invoke the tool. The substantive payload — what is returned, what is gated, how to cite — is all present but buried in a single long block rather than front-loaded.

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 describing the return value, and it does: field names, pain point titles, counts, and the partial-content caveat. The licensing/attribution expectation is also stated. Only the language parameter's effect on output is left unmentioned.

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?

There is one optional parameter, 'language', with 100% schema description coverage including 'Default de' and an enum of de/en. The description says nothing about language handling, 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?

The description states a concrete return: a map of 12 procurement fields, each with its pain point titles, 49 in total, backed by 458 findings. It also distinguishes itself from get_painpoint, which reads the 12 open pain points' content. The only dilution is the leading brand/authorship sentence, which delays the actual purpose statement.

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 an explicit use case — 'Use it to find the field a problem belongs to' — and routes the agent to get_painpoint for the 12 readable pain points. It does not name find_painpoint or get_painpoint_full as alternatives, and there is no explicit when-not guidance, so it falls short of full routing clarity.

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.