Skip to main content
Glama

AICTIONBOT™ Werkbank

Stakeholder map: influence and interest in four fields, attitude, who brings whom along, and a conversation plan in the right order

map_stakeholders
Read-onlyIdempotent

AICTIONBOT™ stakeholder map by KULIC Advisory, built on the Execution Toolkit template T30 (stakeholder mapping). Takes the people involved (name or role, influence 1 to 5, interest 1 to 5, attitude from opponent to champion, whom each person can bring along, their concern and who on the user's side talks to them) and returns the four fields (manage closely, keep satisfied, keep informed, monitor) with a cadence for each, a numbered conversation plan (win influential advocates first, then neutrals through a bridge person, then critics prepared, then the interested), influential critics without a bridge, people without a contact on the user's side and missing values. Recommends roles instead of names when sharing. 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": {
      "stakeholders": "<stakeholders>"
    },
    "name": "map_stakeholders"
  }
}

Input Schema

NameRequiredDescriptionDefault
languageNoLanguage of the answer. Default de.
stakeholdersYesRows: name or role, group, influence (1 to 5), interest (1 to 5), attitude (-2 to 2 or opponent, critical, neutral, supportive, champion), brings_along (names), owner (our contact), concern.

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?

Annotations already cover read-only, idempotent, non-destructive and closed-world, yet the description still adds material context: deterministic with no AI, nothing stored, and a sign-in/latest-licence requirement with a documented free allowance of one check per connection every 30 days. That is exactly the kind of auth and quota information annotations cannot express, and it is consistent with readOnlyHint=true.

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 is front-loaded, but it is one dense run-on paragraph that mixes marketing branding ('AICTIONBOT™ by KULIC Advisory', 'Execution Toolkit template T30') and a long licence clause with the functional content. The licensing sentence in particular could be shortened without losing the signal.

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, so the description carries the return-value burden and does so thoroughly: four named quadrants, per-field cadence, ordered conversation plan logic, and three categories of flagged problems. Combined with a fully documented input schema, an agent has everything needed to call and interpret it; only explicit sibling disambiguation is missing.

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?

With 100% schema coverage the baseline is 3, but the description adds genuine meaning: attitude spans opponent to champion (-2 to 2), influence and interest are 1-5, and each row also carries brings_along, concern and owner on the user's side. It also tells the agent what these inputs produce (quadrant placement, bridging, gap flags), which goes beyond the flat row description 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 specific verb-and-resource pair: it takes the people involved with named attributes and returns four quadrants, a cadence per field, a numbered conversation plan and flagged gaps. That is a distinct job from plan_negotiation or assess_team, so an agent can route to it without opening the 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 strongly implied by 'Takes the people involved' for negotiation/engagement prep, and one advisory rule is given (use roles instead of names when sharing). However, there is no explicit when-to-use versus when-not, and none of the sibling tools (plan_negotiation, assess_team) are named as alternatives, leaving the routing to inference.

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.