Skip to main content
Glama

AICTIONBOT™ Werkbank

Sourcing plan old against new: dropped categories, lowered or removed targets, postponed dates, changed approach, planned effect before and after

compare_sourcing_plans
Read-onlyIdempotent

AICTIONBOT™ sourcing plan comparison by KULIC Advisory (tool 67). Takes the old and the new version of a sourcing plan with one row per category (category, annual volume, approach, savings target in percent, due date, owner) and matches the rows by category. Returns the critical changes (red: a category dropped from the plan, a target removed or cut by a third or more, a due date moved by more than 90 days), the other changes (yellow: moderately lowered target, moved date, changed approach, no owner), raised targets, new categories and changed volumes for information, the planned effect per year before and after (volume times target), the questions to answer before approval and the next step. Pass two arrays (old_rows and new_rows) or one array rows with a version column (Old or New; German: Alt or Neu). Deterministic, no AI, nothing stored. The effect is the plan's own target, not a promise. To work out the route for one category use plan_sourcing. 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

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "compare_sourcing_plans"
  }
}

Input Schema

NameRequiredDescriptionDefault
rowsNoAlternative to old_rows and new_rows: one list with a version column (Old or New) plus the columns above.
languageNoLanguage of the answer. Default de.
new_rowsNoNew version with the same columns.
old_rowsNoOld version: category, volume, approach, target (percent), due (date), owner. German column names work too (warengruppe, volumen, vorgehen, ziel, abschluss, verantwortlich).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the read-only, idempotent annotations, it discloses deterministic operation with no AI or storage, exact red and yellow classification thresholds, the volume-times-target calculation, and the caveat that effect is a plan target rather than a promise. It also documents sign-in, licensing, and the free allowance of one check per connection every 30 days.

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?

Most content is useful, but it is packed into one dense paragraph with a particularly long output enumeration and substantial licensing detail. The opening branding and tool number add little, and separating inputs, outputs, behavior, and access requirements would make the definition easier to scan.

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 complex comparison tool without an output schema, the description supplies the input model, matching rule, output categories, severity thresholds, effect formula, interpretation caveat, operational constraints, and access requirements. Together with the fully described schema and alternative-tool guidance, this is sufficient for correct selection and 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?

Although schema description coverage is 100%, the description adds useful row semantics by enumerating category, annual volume, approach, percentage savings target, due date, and owner, and by explaining category-based matching. It also clarifies the alternative version-column workflow and German version labels, though it does not add details such as accepted date or volume formats.

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 precisely states that the tool compares old and new sourcing-plan versions, matches rows by category, and reports changes plus planned effect before and after. Its detailed change classifications and the pointer to plan_sourcing make its scope readily distinguishable from planning and other comparison siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explains both accepted invocation patterns: supply old_rows and new_rows, or supply rows with an Old/New or Alt/Neu version column. It also gives an explicit alternative, directing agents to plan_sourcing when they need the route for one category rather than an old-versus-new plan comparison.

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.