Skip to main content
Glama

AICTIONBOT™ Werkbank

Segment suppliers by business impact and supply risk: strategic, leverage, bottleneck, transactional, with the way to handle each

segment_suppliers
Read-onlyIdempotent

AICTIONBOT™ supplier segmentation by KULIC Advisory, built on the Execution Toolkit template T12 (supplier segmentation). Takes the user's supplier list or spend export (one row per supplier or per booking; rows of the same supplier are added up) and places every supplier in one of four fields by business impact and supply risk on a 1 to 5 scale: strategic (partnership at management level), leverage (use competition, tender, consolidate), bottleneck (secure supply, develop alternatives) and transactional (catalogue, framework agreement, automation). Impact can be given or is derived from spend (Pareto 80 percent, a share of 10 percent or more counts as very high); risk can be given or is derived from single source, critical part, number of alternatives and lead time. Returns count, spend and share per field, the largest suppliers per field, strategic or bottleneck suppliers without an alternative and the tail below 1 percent of spend. 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": {
      "suppliers": "<suppliers>"
    },
    "name": "segment_suppliers"
  }
}

Input Schema

NameRequiredDescriptionDefault
languageNoLanguage of the answer. Default de.
suppliersYesRows: supplier, category, spend, impact (1 to 5), risk (1 to 5); instead of risk: single_source (yes/no), critical (yes/no), alternatives (count), lead_time_weeks.
thresholdNoScore from which impact and risk count as high. Default 3.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover readOnly, idempotent, non-destructive and closed-world, and the description adds genuinely new behavioral facts beyond them: deterministic computation with no AI, nothing stored, aggregation of duplicate supplier rows, implicit Pareto/lead-time derivation logic, and the licensing/sign-in requirement with the free 30-day check fallback. It also previews what is returned, which is valuable given there is no output schema.

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?

It is front-loaded with the purpose and then proceeds in a logical order: inputs, segmentation logic, derivation rules, outputs, then licensing. The opening brand/template framing ('AICTIONBOT™ ... KULIC Advisory, built on the Execution Toolkit template T12') is overhead for an agent, and the single dense paragraph makes it slower to scan than it needs to be.

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?

For a read-only analytical tool with no output schema, the description supplies everything needed: input shape and aggregation, the four segments with handling advice per segment, derivation rules, the full list of returned artifacts, and access prerequisites. Nothing material about calling it correctly is left unexplained.

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 baseline is 3, but the description adds real meaning by explaining what 'impact' and 'risk' mean when they are derived (Pareto 80 percent, a 10 percent share as very high; single source, critical part, alternatives, lead time) rather than passed in. The threshold parameter is only implicitly covered by the phrase 'by business impact and supply risk on a 1 to 5 scale', so one gap remains.

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?

The description names a specific verb and resource ('supplier segmentation') and enumerates the four output fields (strategic, leverage, bottleneck, transactional) together with the two axes (business impact and supply risk). It is clearly distinguishable from siblings such as analyse_spend or screen_supplier_risk because it states that every supplier is placed in one of four segments and how impact/risk are derived.

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 states the accepted inputs precisely ('supplier list or spend export, one row per supplier or per booking; rows of the same supplier are added up') and gives derivation rules for when impact or risk are not supplied, which tells an agent when the tool applies. It stops short of naming alternatives or exclusions, so the when-not guidance is missing.

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.