Skip to main content
Glama

AICTIONBOT™ Werkbank

Capability gaps per person and team against a role profile: who is ready for more, who needs a coaching plan, three training priorities

assess_team
Read-onlyIdempotent

AICTIONBOT™ capability check by KULIC Advisory, built on the Execution Toolkit templates T16 (competency assessment), T17 (team assessment) and T18 (capability matrix). Takes people with role and self or manager ratings 1 to 5 for ten procurement capabilities (need, market, tender, nego, contract, srm, spend, p2p, risk, stake) or for the user's own profile, compares them with the target per role (buyer, category manager, procurement business partner, S2P lead; suggested targets marked as such) and returns per person the average gap, the largest gaps and a verdict (ready for a stretch role, develop selectively, coaching plan), plus three training priorities for the team and a 30, 60, 90 day path. 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": {
      "people": "<people>"
    },
    "name": "assess_team"
  }
}

Input Schema

NameRequiredDescriptionDefault
peopleYesRows: name (or role label), role, scores {need, market, tender, nego, contract, srm, spend, p2p, risk, stake} each 1 to 5.
profileNoOptional own profile: capability and target level 1 to 5; scores then use the capability names as keys.
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?

Goes well past the annotations by declaring the tool is deterministic with no AI, stores nothing, and requires an AICTIONBOT™ Werkbank licence with a specific free path (one check per connection every 30 days, 'Connect without a licence'). Those are exactly the operational facts an agent needs and none are derivable from readOnlyHint/idempotentHint.

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 core behaviour is front-loaded and dense with useful detail, but the opening brand/licence boilerplate ('AICTIONBOT™ ... built on the Execution Toolkit templates T16, T17, T18') is marketing filler that does not help an agent decide or invoke. It is a single long run-on paragraph with no separation between purpose, inputs and licensing.

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 return-value burden and does it well: per-person gaps, a verdict from three named buckets, three team training priorities, and a 30/60/90-day path. Inputs, auth and determinism are all covered; only edge cases (invalid ratings, rows exceeding the capability set) are 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 baseline is 3; the description still adds real meaning by naming all ten capability keys, the four role profiles with the note that suggested targets are marked, and that profile mode switches scoring to capability-name keys. It does not explain the row structure or the 200/30 limits, but those are already in the schema.

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 chain and resource: takes people with 1–5 ratings on ten named procurement capabilities, compares them to per-role targets, and returns per-person average gap, largest gaps and a verdict plus team training priorities. The enumerated capability keys, role types and verdict buckets make the tool's scope unmistakable and leave no sibling ambiguity.

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 through input requirements (people with ratings, or the user's own profile via `profile`) and through the licence/sign-in condition, which tells the agent what is needed before calling. However, it never states when to prefer this over an alternative, nor any when-not-to-use condition beyond the free-tier limit.

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.