Skip to main content
Glama

add_business_days

Read-onlyIdempotent

Add business days to a start date while skipping weekends and public holidays for US, UK, FR, DE, or JP calendars, so you can compute deadlines that exclude non-working days.

Instructions

Adds N business (working) days to a start date, skipping weekends and country-specific public holidays. Supports US, UK, FR, DE, and JP holidays. Returns the resulting date. Use when computing a deadline that excludes non-working 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": {
      "start_date": "<start_date>",
      "days": "<days>"
    },
    "name": "add_business_days"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysYesNumber of business days to add (negative to subtract). Integer between -100000 and 100000.
countryNoISO-3166-1-alpha-2 country code for holiday calendar. Supported holiday sets: US, UK, FR, DE, JP; other valid 2-letter codes fall back to weekend-only counting and say so in holidaySupport.US
start_dateYesISO date string for the start date.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv0.8.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedInput schema / properties / country / description
      Previous value: -"ISO-3166-1-alpha-2 country code for holiday calendar."New value: +"ISO-3166-1-alpha-2 country code for holiday calendar. Supported holiday sets: US, UK, FR, DE, JP; other valid 2-letter codes fall back to weekend-only counting and say so in holidaySupport."
    • addedInput schema / properties / country / pattern
      Added value: +"^[A-Za-z]{2}$"
    • changedInput schema / properties / days / description
      Previous value: -"Number of business days to add (negative to subtract)."New value: +"Number of business days to add (negative to subtract). Integer between -100000 and 100000."
    • addedInput schema / properties / days / maximum
      Added value: +100000
    • addedInput schema / properties / days / minimum
      Added value: +-100000
    • changedInput schema / properties / days / type
      Previous value: -"number"New value: +"integer"
  2. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful behavior — weekend and holiday skipping, the five supported holiday calendars, and that a date is returned — but omits what happens with an unsupported country code (weekend-only fallback), which is the main non-obvious behavior for this tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short sentences, front-loaded with the core operation and followed by supported calendars, return value, and usage trigger. Nothing is redundant, and 'Returns the resulting date' earns its place because no output schema exists.

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 correctly states the return value, and the input schema fully documents the three parameters. The only meaningful gap is edge-case behavior around the start date and unsupported country handling, which an agent might want spelled out for a date-arithmetic 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 description coverage is 100%, so the schema already explains days (including negative subtraction) and the country code fallback in detail. The description reinforces the country parameter by listing the supported holiday sets, but adds no syntax or edge-case meaning beyond what the schema states; baseline 3 applies.

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 gives a specific verb and resource ('Adds N business (working) days to a start date') plus a clear scope: weekends and country-specific holidays are skipped. It is naturally distinguishable from count_business_days by verb (add vs. count), but it never names or contrasts that sibling explicitly, so it falls short of the top score.

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?

The final sentence supplies a concrete use case ('Use when computing a deadline that excludes non-working days'), which is enough for an agent to route correctly. It offers no when-not guidance and does not point at alternatives such as count_business_days or time_math for other date arithmetic.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.