Skip to main content
Glama

AICTIONBOT™ Werkbank

Scope of work old against new: dropped services, new restrictions, new duties for the customer and changed figures, section by section

compare_scope_of_work
Read-onlyIdempotent

AICTIONBOT™ scope of work comparison by KULIC Advisory (tool 69). Takes the full text of the old and the new version of a scope of work, service description or statement of work. Splits both into sections, matches them by wording, number and similarity and returns: dropped sections (red), changed sections with the sentences before and now, the figures, quantities, deadlines and dates that differ, new restrictions such as not included, at extra cost, on request or best effort, and new duties for the customer (all red), other changes and new sections (yellow), ready questions for the other side and the next step. It shows what changed in the wording, not what it means legally. Deterministic, no AI, nothing stored. Not legal advice. To compare two contract versions use compare_contracts, to write a scope of work use write_scope_of_work. 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_scope_of_work"
  }
}

Input Schema

NameRequiredDescriptionDefault
languageNoLanguage of the answer. Default de.
new_textNoFull text of the new version.
old_textNoFull text of the old (previous) version.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behaviour; the description adds what they cannot: deterministic processing, no AI, nothing stored, not legal advice, and licence gating. The only gap is no note on runtime, size limits (the 400k char caps live only in schema), or failure behaviour for empty/identical inputs.

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 core sentence and the returns list are well front-loaded and information-dense, but the definition is padded with branding ('AICTIONBOT™ by KULIC Advisory (tool 69)'), a repeated not-legal-advice note, and a long licensing paragraph. These earn their place only partially, mostly for the auth requirement.

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 comparison tool with no output schema, the description enumerates the return categories thoroughly, plus auth, storage and legal caveats, so an agent knows what comes back. Missing details are input-size handling and behaviour when texts differ little or are empty.

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 earns a bit more by clarifying that old_text and new_text are the full texts of the old and new version and that comparison is wording-level, not legal meaning. The language parameter and its de default are left entirely to the schema, but that is acceptable at full coverage.

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?

Names a specific verb and resource (compares old vs new scope of work section by section) and enumerates the returns: dropped sections, changed sentences, differing figures/deadlines, new restrictions, new customer duties. It explicitly separates itself from compare_contracts and write_scope_of_work, so the agent can pick correctly without opening schemas.

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?

Gives explicit routing: use compare_contracts for two contract versions and write_scope_of_work to author one. It also states prerequisites (AICTIONBOT Werkbank licence, free check per connection every 30 days, 'Connect without a licence' path), which tells the agent both when to use it and what blocks invocation.

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.