Skip to main content
Glama

business-deadline

Business-day deadline (clear days, cutoffs, DST) on a named or caller calendar — Computes the date (and optionally the instant) a business-day deadline falls on, for an agent drafting or checking a contract, notice, SLA or partner response window: '10 clear business days' (both endpoints excluded) or 'within 10 business days' (end day counted), forward or backward, with an after-cutoff roll, caller or named holiday calendar and a DST-aware deadline time. Named calendars (US fe

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": {
      "start": "<start>",
      "days": "<days>",
      "counting": "<counting>",
      "calendar": "<calendar>"
    },
    "name": "business-deadline"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysYes
startYesLocal date YYYY-MM-DD, or local date-time YYYY-MM-DDTHH:MM[:SS] (the notice/receipt moment). Never read from the clock.
cutoffNoLocal HH:MM. With a date-time start (direction after), a start strictly later than the cutoff, or on a non-business day, is deemed received on the next business day. 17:00 exactly is on time. Without cutoff there is no roll.
weekendNoNon-business weekdays, 0=Sunday..6=Saturday. Default [0, 6]; use [5, 6] for a Friday/Saturday weekend.
calendarYesNamed holiday calendar with a source and supported date range (outside it the answer is unsupported), weekends-only (Saturday/Sunday only), or caller (only the holidays you list).
countingYesclear: days strictly between start and deadline, so the deadline is business day N+1. elapsed: the deadline is business day N after start (the end day is counted).
holidaysNoExtra non-business dates YYYY-MM-DD (company closures, a calendar we do not carry).
timeZoneNoIANA zone for deadlineTime.
directionNoDefault after. before counts backward from start (for 'at least N days before the hearing').
deadlineTimeNoLocal HH:MM at which the deadline expires on the deadline date; needs timeZone to produce an instant.
disambiguationNoHow to read a deadline time that falls in a DST gap (earlier: before-gap offset reading backward; later: shifted forward) or overlap (earlier/later occurrence). Without it, a gap or overlap returns unknown with both candidates.
claimedDeadlineNoA deadline date someone asserted; the check fails with the computed date if it differs.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the after-cutoff roll, the DST gap/overlap fallback ("returns unknown with both candidates"), that dates outside a named calendar's supported range are unsupported, and that a mismatched claimedDeadline fails with the computed date. The dangling final clause "Named calendars (US fe" truncates the one piece of calendar behavior it was about to explain.

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?

It is front-loaded with the verb-resource statement and packs a lot of meaning per clause with little waste. However, it is one long run-on sentence with dense parentheticals, and the final sentence is cut off mid-word, which weakens structure.

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 12-parameter tool with no output schema, the description covers the mechanics (counting, roll, DST, calendars, verification) that an agent would otherwise have to guess, and the high schema coverage fills in the field-level detail. The truncation and the absence of any statement about the return shape leave small but real gaps.

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 description coverage is already 92%, so a 3 is the baseline, but the description adds genuine meaning on top: it ties counting=clear/elapsed to the concrete legal phrasings and their endpoint treatment, and explains the cutoff roll and DST-aware deadline time. The truncated closing sentence leaves the named-calendar semantics partly unexplained.

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?

The description opens with a specific verb and resource: "Computes the date (and optionally the instant) a business-day deadline falls on," and scopes it to contracts, notices, SLAs and response windows. It does not explicitly contrast itself with the sibling deadline-feasibility, so an agent must infer the boundary, but the core purpose is unmistakable.

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?

It names the concrete scenarios in which to reach for this tool (drafting or checking a contract, notice, SLA, partner response window) and explains which counting mode matches which phrasing ("10 clear business days" vs "within 10 business days"). It offers no negative guidance on when to prefer deadline-feasibility or another sibling instead.

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.

Resources