Skip to main content
Glama

AICTIONBOT™ Werkbank

Draft a mutual or one-way non-disclosure agreement (NDA) from the KULIC Advisory NDA template

create_nda
Read-onlyIdempotent

KULIC Advisory, AICTIONBOT™ Workbench. Drafts a non-disclosure agreement in German or English from the KULIC Advisory NDA template (Execution Toolkit Library T22): mutual or one-way, two parties with address and representative, purpose, effective date, confidentiality term of 1, 2, 3 or 5 years, governing law and an optional place of jurisdiction. Returns the full text with ten sections and signature blocks, ready to paste into a document or email, and the link to the free web tool that creates the same agreement as Word and PDF in the browser and sends it from the user's own email app. Deterministic, no AI, nothing stored. Working template, not legal advice. 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": {
      "party_a": "<party_a>",
      "party_b": "<party_b>"
    },
    "name": "create_nda"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNomutual: both parties share information (default). one_way: only party A discloses, party B receives.
yearsNoConfidentiality term in years. Default 3.
party_aYesParty A (in a one-way NDA the disclosing party).
party_bYesParty B (in a one-way NDA the receiving party).
purposeNoPurpose in one sentence. Default: evaluation of a possible collaboration.
languageNoLanguage of the agreement and the answer. Default de.
jurisdictionNoOptional place of jurisdiction, for example Cologne.
governing_lawNogermany (default), austria, switzerland, england_wales, or the name of another jurisdiction.
effective_dateNoEffective date as YYYY-MM-DD. Default: today.

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?

Goes well beyond the annotations (readOnlyHint/​idempotentHint true, destructiveHint false) by disclosing that output is full contract text plus a web-tool link, that execution is deterministic with no AI and nothing stored, and that the text is a working template rather than legal advice. It also surfaces the auth/rate-limit model explicitly — licence required, otherwise one free check per connection every 30 days via 'Connect without a licence' — which the annotations do not carry at all. No contradiction: returning text is consistent with readOnlyHint.

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 purpose is front-loaded, which is good, but the paragraph then bundles output format, a promotional description of the companion web tool, template provenance, determinism, disclaimer and licensing into one run-on block. The 'KULIC Advisory, AICTIONBOT™ Workbench' framing and the web-tool sales copy consume space that could have carried parameter or failure guidance instead.

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 9-parameter tool with nested party objects and no output schema, the description covers what comes back (ten sections plus signature blocks), the defaults, and the auth/licence prerequisite — the pieces an agent needs to call it and set expectations. The remaining gap is that it says nothing about behaviour on invalid input or what the response looks like when licence checks fail.

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% and every enum and default (kind, years 1/2/3/5, language, governing_law, effective_date) is already documented in the schema. The description restates the same field semantics — parties with address and representative, purpose, effective date, term, governing law, optional place of jurisdiction — without adding format, constraint, or interaction details the schema lacks. Baseline 3 is appropriate.

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?

States a specific verb and resource: 'Drafts a non-disclosure agreement in German or English from the KULIC Advisory NDA template (Execution Toolkit Library T22)', plus the mutual/one-way variants and the ten-section output. It does not name or distinguish itself from plausible siblings such as get_template or fill_template, leaving the agent to infer that this tool is the end-to-end drafting path rather than the raw template fetch.

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?

Usage is only implied by the resource name — an agent can infer 'use this when you need an NDA'. There is no explicit when-not-to-use, no routing to get_template/fill_template for other document types, and no statement about what to do if the party data is missing. The only real routing hint is that the free web tool produces Word/PDF, which points at the browser rather than a sibling tool.

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.