Skip to main content
Glama

AICTIONBOT™ Werkbank

Business case for a procurement improvement: annual value band, ROI band, payback band and where the value comes from

build_business_case
Read-onlyIdempotent

From the user's own assumptions (annual addressable spend, estimated value leakage, annual transactions, minutes of manual effort per transaction, hourly cost, error or rework rate, planned investment and a scenario) it returns directional bands, never exact promises: annual value band, ROI band, payback band, economic relevance, where the value comes from (shares of manual effort, rework and value leakage) and the cost of waiting per week as a band. Same formula and bands as the ROI calculator on kulicadvisory.com. Needs the investment, a scenario and either spend with a leakage rate or transactions with minutes and hourly cost; with spend given, a missing leakage rate, investment or scenario is filled with a marked example value (1.5 %, EUR 75,000, realistic). Directional and based on user-entered assumptions only; not a guarantee of results. Licence, or one free check every 30 days.

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": "build_business_case"
  }
}

Input Schema

NameRequiredDescriptionDefault
languageNoLanguage of the answer. Default de.
scenarioNoHow much of the gross potential is assumed to be reachable: conservative 25 %, realistic 50 %, ambitious 75 %.
investment_eurNoEstimated implementation or advisory investment in EUR.
hourly_cost_eurNoFully loaded hourly cost in EUR.
leakage_percentNoEstimated value leakage in percent of that spend, e.g. 1.5.
annual_spend_eurNoAnnual addressable spend in EUR.
error_rate_percentNoEstimated error or rework rate in percent.
annual_transactionsNoTransactions per year, e.g. invoices or purchase orders.
minutes_per_transactionNoAverage manual effort per transaction in minutes.

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?

Beyond the readOnly/idempotent annotations it discloses key behaviors: answers are directional bands rather than exact figures, missing inputs are silently replaced by a marked example value (1.5 %, EUR 75,000, realistic), and access is gated by a licence or one free check per 30 days. It also states the output is deterministic in the same way as the website calculator, which helps the agent interpret repeat calls.

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?

Dense but front-loaded: the input list, then the return shape, then the requirements, then caveats. The opening parenthetical parameter recital is heavy and the final sentence repeats the earlier 'never exact promises' disclaimer, costing some tightness.

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 nine optional parameters and no output schema, the description carries the burden well: it explains what comes back, what gets defaulted, and what the caveats are. Nothing an agent needs in order to call it correctly appears to be 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?

Schema coverage is 100%, so the baseline is 3; the description adds value by grouping the parameters into named assumptions and explaining the conditional dependency between the spend/leakage path and the transactions/minutes/hourly-cost path, which the flat schema cannot express. It stops short of adding units or format hints beyond what the schema already documents.

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 concrete verb+resource (build a business case for a procurement improvement) and enumerates the exact outputs: annual value band, ROI band, payback band, economic relevance, value-source shares and cost of waiting. An agent can tell this apart from siblings such as track_value or check_kpis, which do not model scenarios or return bands.

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?

Clearly specifies the required inputs and the two alternative input routes (spend + leakage rate, or transactions + minutes + hourly cost), plus the fallback when spend is given but leakage, investment or scenario is missing. It does not name when to prefer a sibling tool instead, so it falls short of full when/when-not guidance.

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.