Skip to main content
Glama

AICTIONBOT™ Werkbank

Prepare a supplier negotiation: goal, alternative, opening position, concessions and answers to objections (AICTIONBOT™ negotiation sparring)

plan_negotiation
Read-only

Needs the user's AICTIONBOT™ Werkbank licence; each call uses one AI analysis from the licence quota. Builds a negotiation plan for the buyer: the goal, the best alternative if there is no agreement, a recommended opening position, the walk-away point, concessions with what to ask in return, likely supplier objections with answers, an opening sentence and traps to avoid. Uses only the numbers the buyer gives; where a fact is missing it leaves a placeholder. Negotiation guidance from an experienced buyer, not legal advice and no promise of outcome. The input is processed for this answer only and is not stored by KULIC Advisory.

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": {
      "what_is_bought": "<what_is_bought>"
    },
    "name": "plan_negotiation"
  }
}

Input Schema

NameRequiredDescriptionDefault
goalNoOptional: what the buyer wants to reach.
languageNoLanguage of the answer: de, en, fr, es, pt or zh. Default de.
supplierNoOptional: type of supplier and relationship, e.g. 'regional manufacturer, supplier for six years'. No need for a real name.
walk_awayNoOptional: the point at which the buyer walks away.
what_is_boughtYesWhat the negotiation is about, e.g. 'Packaging film, 40 t a year, supplier announces 9 % more from January'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=true, openWorldHint=true), the description discloses real behavioral facts: a licence is required, each call burns one AI analysis from the quota, only buyer-supplied numbers are used with placeholders for gaps, no data is stored, and it is guidance not legal advice with no outcome promise. It does not describe failure behavior when the licence or quota is exhausted, which is the one meaningful gap for a quota-metered tool.

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?

Front-loaded with the licence prerequisite, then the deliverable list, then constraints and disclaimer. Dense and mostly waste-free, though the long comma-separated enumeration of plan components plus the trailing privacy sentence makes it denser than it needs to be.

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 no output schema, the description compensates by enumerating the parts of the returned plan, and it covers the licence prerequisite, data handling and liability framing. It stops short of stating answer format, length, or what happens on quota exhaustion, which an agent deciding to retry would want.

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?

Schema description coverage is 100%, so every parameter including the language enum is already documented in the schema; the description adds only the general rule that missing facts become placeholders. That signals optional fields may be omitted without hallucination, but no field-specific meaning is added beyond the schema.

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 specific verb and artifact ('Builds a negotiation plan for the buyer') and then enumerates exactly what the plan contains: goal, best alternative, opening position, walk-away point, concessions with trades, objections with answers, opening sentence, traps. That enumeration distinguishes it from evaluate_negotiation and negotiation_round without needing their schemas.

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 preparation-before-a-negotiation context is implied by the output list, and the licence/quota prerequisite is stated explicitly. However, there is no explicit when-to-use versus when-not guidance and no naming of the sibling tools (evaluate_negotiation, negotiation_round) that an agent should pick instead once a plan exists or after the talk has happened.

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.