Skip to main content
Glama

AICTIONBOT™ Werkbank

Check a whole contract list: notice deadlines in the next days, silent renewals, missed deadlines, contracts without an owner

check_contracts
Read-onlyIdempotent

AICTIONBOT™ contract register check by KULIC Advisory, built on the Execution Toolkit template T20 (contract management). Takes the user's contract list (one row per contract) and returns, sorted by urgency: notice deadlines within the window (default 90 days, under 14 days flagged as urgent), contracts whose deadline was missed and that renew silently with the next possible notice date, contracts that end by themselves, gaps in the list (no end date, no notice period, no renewal rule), contracts without an owner and the annual value at stake. Per contract: name, supplier, start or end, initial term, renewal (months or yes/no), notice period (e.g. 3 months, 6 weeks, 30 days), owner, annual value, status (cancelled). German or English column names are recognised (Vertrag, Lieferant, Beginn, Ende, Laufzeit, Verlängerung, Kündigungsfrist, Verantwortlich, Jahreswert). The deadline is the last day notice must reach the other party, calculated as in calculate_notice_deadline. Deterministic, no AI, nothing stored. 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": {
      "contracts": "<contracts>"
    },
    "name": "check_contracts"
  }
}

Input Schema

NameRequiredDescriptionDefault
as_ofNoReference date, YYYY-MM-DD. Default today (Europe/Berlin).
languageNoLanguage of the answer. Default de.
contractsYesContract rows: name, supplier, start (date), end (date), initial_term_months, renewal_months (or auto_renewal yes/no, yes = 12 months), notice (e.g. '3 months', '6 weeks', '3m'), owner, annual_value, status. Dates as YYYY-MM-DD or DD.MM.YYYY.
window_daysNoDays ahead that count as due. Default 90.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the annotations by declaring determinism ('no AI'), that nothing is stored, that it is not legal advice, and the exact licensing/auth path including the free-tier limit of one check per connection every 30 days. Annotations already cover read-only and idempotence, and the description adds the deadline definition (last day notice must reach the other party) and output ordering by urgency.

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 substantive content is front-loaded and dense, but the opening branding ('AICTIONBOT™ ... built on the Execution Toolkit template T20') and the long comma-run sentence make it harder to scan than necessary. Almost every clause carries information, yet the single unbroken paragraph could be split or trimmed of vendor boilerplate.

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

Completeness5/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 supplies the full returned-field inventory per contract and the urgency ordering, so the agent knows what comes back. Licensing, sign-in, reference date behaviour, and language defaults are all covered, leaving no material gap for a read-only batch check of this complexity.

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 extra by listing the accepted German and English column aliases (Vertrag, Lieferant, Kündigungsfrist, Jahreswert) and the notice-period formats, which the schema only sketches. It also restates defaults (90 days, urgent under 14) that the schema already documents, so it adds meaning without being fully additive.

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 resource ('contract register check') and enumerates exactly what the check produces: notice deadlines, silent renewals, missed deadlines, contracts without an owner, and value at stake. It is clearly distinguishable from the sibling calculate_notice_deadline, which it cites only as the calculation rule, and from single-contract tools by insisting on 'the user's contract list (one row per contract)'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Makes the input context explicit ('takes the user's contract list, one row per contract') and explains the default 90-day window plus the under-14-days urgent flag, so an agent knows when this batch check applies rather than the per-contract deadline tool. It never states an exclusion or names an alternative for a single contract, so a small inference is still required.

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.