Skip to main content
Glama

AICTIONBOT™ Werkbank

Calculate the last day to give notice on a contract

calculate_notice_deadline
Read-onlyIdempotent

From contract start, initial term, automatic renewal and notice period it calculates the current term end, the last day notice must reach the other party, the days left and what happens if the date is missed. Deterministic, no AI. Not legal advice: the wording of the contract decides. Licence, or one free check every 30 days.

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": {
      "contract_start": "<contract_start>",
      "initial_term_months": "<initial_term_months>",
      "notice_period": "<notice_period>"
    },
    "name": "calculate_notice_deadline"
  }
}

Input Schema

NameRequiredDescriptionDefault
todayNoOptional reference date, YYYY-MM-DD. Default today (Europe/Berlin).
languageNoLanguage of the answer. Default de.
notice_periodYesNotice period before the end of the term: number plus unit d (days), w (weeks) or m (months), e.g. 3m.
contract_startYesFirst day of the contract, YYYY-MM-DD.
renewal_monthsNoAutomatic renewal period in months after the initial term; 0 if the contract ends without renewal. Default 12.
initial_term_monthsYesInitial (minimum) term in months.

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?

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds real context beyond that: deterministic with no AI, not legal advice because the contract wording governs, and a usage limit of one free check per 30 days. It also sketches what the response reports, though it does not describe output structure in detail.

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 core capability is front-loaded in the opening clause and every later sentence carries distinct value (determinism, legal caveat, quota). The first sentence is long and stacks four outputs, but nothing is redundant.

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 usefully enumerates what is returned (term end, notice deadline, days remaining, consequence of missing it), which compensates for the missing response contract. It stops short of explaining edge cases such as renewal=0 producing an ending contract, so it is strong but not fully complete for a 6-parameter calculation tool.

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 coverage is 100%, so every parameter is already documented, and the description adds little beyond naming the four core drivers (start, initial term, renewal, notice period). It never addresses the optional today reference date or the language switch, so it does not exceed the schema baseline.

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?

The description names a specific computation (term end, last day notice must reach the other party, days left, consequence of missing the date) rather than restating the name. An agent can tell this apart from review_contract or check_contracts because it produces a deadline calculation, not a document review.

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 through the required inputs (start, initial term, renewal, notice period), which signal the calculation scenario. There is no explicit statement of when to prefer this tool over contract-review siblings, nor any when-not guidance; the only gating mentioned is the licence/free-check quota.

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.