Skip to main content
Glama

AICTIONBOT™ Werkbank

Rate suppliers with a scorecard: points and class A to D, trend against the previous period, figures below target, three measures for the supplier meeting

rate_supplier
Read-onlyIdempotent

AICTIONBOT™ supplier scorecard by KULIC Advisory, built on the Execution Toolkit template T13 (supplier performance evaluation). Takes one row per supplier and period with on-time delivery (percent), defect rate (percent) or ppm, complaints (count, with deliveries per period for a rate), price change (percent) and cooperation (1 to 5), and returns per supplier points out of 100, a class (A from 85, B from 70, C from 50, D below), the trend against the previous period, the figures below target and three concrete measures for the weakest figures. Targets: on-time at least 95 %, defects at most 1 %, at most 1 complaint per 100 deliveries, price change at most 3 %, cooperation at least 4. The last row per supplier is the current period. German or English column names are recognised (Lieferant, Zeitraum, Liefertreue, Fehlerquote, Reklamationen, Lieferungen, Preisänderung, Zusammenarbeit). 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": {
      "rows": "<rows>"
    },
    "name": "rate_supplier"
  }
}

Input Schema

NameRequiredDescriptionDefault
rowsYesRows: supplier, period, on_time (percent), quality (defect percent) or ppm, complaints, deliveries, price_change (percent), service (1 to 5). Oldest period first.
weightsNoOptional weights: on_time, quality, complaints, price, service. Default 35, 30, 15, 10, 10.
languageNoLanguage of the answer. Default de.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

The annotations already establish that this is a read-only, idempotent, non-destructive, closed-world operation. The description adds meaningful operational context beyond those annotations: deterministic behavior, no AI use, no storage, and a licensing/sign-in requirement with a free 30-day check. It stops short of describing failure modes or response structure, but the added transparency is substantial.

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?

The description is dense but appropriately sized for a multi-parameter scorecard tool with detailed inputs and outputs. It is front-loaded with the scorecard purpose, though the branding and template reference add minor non-essential wording and the paragraph could be more clearly structured.

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?

Given the tool's complexity, the absence of an output schema, and the need to understand scoring targets and period handling, the description is complete. It explains inputs, scoring semantics, returns, targets, recognized column names, and licensing constraints, leaving no critical gap for correct invocation.

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 already 100%, so the baseline is 3. The description adds useful meaning beyond the schema by explaining the row fields in business terms, the current-period convention, the target thresholds, and the recognized German/English column names. It does not mention the optional weights parameter, but the schema documents that fully.

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 states a specific verb and resource: it produces a supplier scorecard with points out of 100, class A to D, trend, below-target figures, and concrete measures. This is clearly distinguishable from sibling tools such as screen_supplier_risk or segment_suppliers, which serve different supplier-analysis purposes.

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?

The description implies when the tool is used, namely for supplier performance evaluation using one row per supplier and period, and it gives detailed input conditions such as the last row being the current period. However, it does not explicitly state when to choose this tool over related alternatives, so usage guidance remains implied rather than comparative.

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.