Skip to main content
Glama

AICTIONBOT™ Werkbank

Compare commercial scenarios: volume against price, tiers, one-off costs, freight, rebate and cash discount, with the cheapest offer per volume range

compare_scenarios
Read-onlyIdempotent

AICTIONBOT™ scenario calculator by KULIC Advisory, built on the Execution Toolkit template T14 (supplier commercial scenarios). Takes up to 12 offers with a unit price or price tiers (all-units or incremental), one-off costs such as tooling or setup, freight per unit, a volume rebate with its threshold and a cash discount, and the volumes to compare. Returns the total cost and cost per unit for each offer and volume, the cheapest offer per volume range with the exact tipping points, and for the negotiation the unit price each other offer would need to match the cheapest at the reference volume (useful as input for the negotiation sparring). 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": {
      "offers": "<offers>"
    },
    "name": "compare_scenarios"
  }
}

Input Schema

NameRequiredDescriptionDefault
offersYesOne object per offer: supplier, unit_price or tiers [{from, price}], tier_mode (all_units or incremental, default all_units), fixed_cost, freight_per_unit, bonus_percent, bonus_from (volume), payment_discount_percent.
languageNoLanguage of the answer. Default de.
quantitiesNoVolumes to compare, e.g. [500, 1000, 2000]. Default: the tier thresholds.
reference_qtyNoVolume for the negotiation targets; must be one of quantities. Default: the largest.

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 readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavior: deterministic with no AI, nothing stored, and an authentication/quota story (licence required, one free check per connection per 30 days). That is exactly the kind of context annotations cannot express.

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 functional content is front-loaded and dense, but the opening clause ('AICTIONBOT™ scenario calculator by KULIC Advisory, built on the Execution Toolkit template T14') is branding that does not help an agent decide or call correctly. The licence sentence is long and partly redundant with itself.

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?

With no output schema, the description carries the return-value burden and does so concretely: totals, cost per unit, cheapest offer per range, tipping points, and match prices. Inputs, limits, determinism and access requirements are all covered, so an agent has everything needed to call it correctly.

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 description coverage is 100%, so the baseline is 3. The description still adds interpretive meaning the schema only abbreviates: that tiers can be all-units or incremental, that the rebate has a volume threshold, that payment_discount is a cash discount, and that the comparison volumes drive the per-volume cost table.

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 names a concrete verb and resource set: it compares up to 12 offers with unit price or tiers, one-off costs, freight, rebate and cash discount, and states the returns (total cost, cost per unit, cheapest offer per volume range, tipping points, negotiation match prices). That is far more specific than the title alone. The gap is sibling differentiation: 'compare_offers' exists in the catalog and the description never says how this differs from it.

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 rather than stated: needing total cost and cheapest-per-volume across suppliers, plus the aside that match prices are 'useful as input for the negotiation sparring'. There is no explicit when-to-use versus when-not, and no routing away from 'compare_offers' or 'evaluate_negotiation'.

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.