Skip to main content
Glama

AICTIONBOT™ Werkbank

Request to offer: a dated route from a customer request through supplier quotes to the company's own offer, with RFQ and reminder texts and the selling price

plan_request_to_offer
Read-onlyIdempotent

AICTIONBOT™ request to offer by KULIC Advisory (tool 50), built on the Execution Toolkit templates T10 (RFQ) and T11 (sourcing evaluation). For traders and job shops: takes the customer request (item, customer, quantity, unit, customer deadline), the mark-up and optional supplier offers (supplier, unit price, delivery days, valid until). Returns a dated route (send request today, reminder, compare, offer to the customer), the offers with validity and lead time checks, the cheapest valid offer, the selling price with mark-up and gross margin, and RFQ and reminder texts in German and English to copy. Nothing is sent. 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": {
      "request": "<request>"
    },
    "name": "plan_request_to_offer"
  }
}

Input Schema

NameRequiredDescriptionDefault
unitNoUnit, for example piece or kg.
as_ofNoReference date, YYYY-MM-DD. Default today.
marginNoMark-up on the purchase price in percent. Default 15.
offersNoOptional supplier offers: supplier, unit_price, delivery_days, valid_until (YYYY-MM-DD). German column names work too.
requestYesWhat the customer asks for.
customerNoCustomer name.
languageNoLanguage of the answer. Default de.
quantityNoQuantity.
customer_deadlineNoDate the customer expects the offer, YYYY-MM-DD.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior5/5

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

Beyond the annotations (readOnly, idempotent, closed-world), the description discloses that 'Nothing is sent', that the computation is deterministic with no AI and nothing stored, and it spells out the authentication requirement including the licence and the 30-day free-check fallback. That is exactly the extra context an agent needs before invoking, and nothing contradicts the readOnly/idempotent hints.

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 content is front-loaded on the return value, which is useful for a no-output-schema tool, but it is padded with branding ('AICTIONBOT™ by KULIC Advisory (tool 50)') and internal template references (T10/T11) that do not help an agent select or call it. Sentences are long and dense, packing outputs, auth and side-effect notes into one paragraph.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 9 parameters but only 1 required and no output schema, the description covers the gap well by enumerating what comes back: the dated route, validity and lead-time checks, cheapest valid offer, selling price with mark-up and margin, and bilingual texts. Auth and side-effect behaviour are also covered; only the mark-up/gross-margin calculation semantics remain lightly specified.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With schema description coverage at 100%, the schema already documents each of the 9 parameters, including defaults for as_of, margin and language and the German column-name tolerance. The description adds only a paraphrased list of the same fields plus the note that offers are checked for validity and lead time, so it stays at the baseline rather than adding deeper semantics.

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 chain — takes a customer request, mark-up and optional supplier offers, and returns a dated route, priced offer and RFQ/reminder texts. That is far more specific than the cryptic tool name 'plan_request_to_offer'. It stops short of explicitly distinguishing itself from siblings such as create_rfq or plan_sourcing, so an agent must infer the boundary.

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?

It names a target audience ('For traders and job shops') and enumerates the prerequisites (customer request fields, mark-up, optional offers), which implies when the tool applies. However, there is no explicit when-not guidance and no named alternative such as create_rfq or plan_sourcing to route an agent away when the situation does not fit.

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.