Skip to main content
Glama

AICTIONBOT™ Werkbank

Evaluate the practised negotiation: grade, what went well, what to improve and one sentence for the real meeting (AICTIONBOT™ negotiation sparring)

evaluate_negotiation
Read-only

Needs the user's AICTIONBOT™ Werkbank licence; each call uses one AI analysis from the licence quota. Evaluates a practised negotiation from the buyer's side: a grade (very good, good, solid or needs work), what was reached, what the buyer did well, what to improve and one sentence for the real meeting. Pass the situation and the full transcript of the practice. Negotiation guidance, not legal advice. The transcript 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>",
      "transcript": "<transcript>"
    },
    "name": "evaluate_negotiation"
  }
}

Input Schema

NameRequiredDescriptionDefault
goalNoOptional: what the buyer wanted to reach.
languageNoLanguage of the answer: de, en, fr, es, pt or zh. Default de.
supplierNoOptional: type of supplier.
walk_awayNoOptional: the buyer's walk-away point.
transcriptYesThe practised conversation, oldest first.
what_is_boughtYesWhat the negotiation was about.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

The annotations cover read-only and non-destructive behaviour, and the description adds material the annotations cannot: a Werkbank licence is required, each call consumes one AI analysis from the quota, the transcript is processed but not stored, and output is negotiation guidance rather than legal advice. The quota consumption is a notable side effect for a readOnlyHint tool and is well disclosed; only the response structure's limits (e.g. no length or failure behaviour) remain uncovered, which is minor since the deliverable is fully described.

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?

The text is dense but every sentence carries payload: licensing, output components, required inputs, disclaimer, and data handling. The one weakness is ordering, since the licence and quota notice leads ahead of the actual purpose, which should be front-loaded for faster tool selection.

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?

For a six-parameter analysis tool with no output schema, the description supplies the deliverable, the required inputs, the licence prerequisite and quota cost, plus privacy and non-legal-advice caveats. The only gap is what happens on licence exhaustion or an invalid transcript, which an agent might want to know before calling.

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 goal, walk_away, supplier, language and transcript structure is already documented in the schema. The description only reinforces "the situation and the full transcript", adding no new format or constraint detail beyond what the schema states, so the baseline of 3 applies.

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?

"Evaluates a practised negotiation from the buyer's side" states a specific verb and resource, and the description enumerates the exact outputs (grade, what was reached, what went well, what to improve, one sentence for the real meeting). It is clearly a post-practice review tool rather than a live negotiation step like plan_negotiation or negotiation_round, though no sibling is named explicitly.

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?

"Pass the situation and the full transcript of the practice" gives an intake instruction and "a practised negotiation" implies this is used after a sparring round, not during one. There is no explicit statement of when not to use it or which sibling to pick instead (e.g. plan_negotiation for preparation), so the agent must infer the boundary.

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.