Skip to main content
Glama
Sign In
TimezoneToolkit MCP Server

TimezoneToolkit MCP Server

by Cicatriiz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

calculate_business_days

Calculate business days between two dates, excluding weekends and optionally US holidays. Specify timezone for precise results.

Instructions

Calculate business days between two dates (excluding weekends)

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": {
      "startDate": "<startDate>",
      "endDate": "<endDate>"
    },
    "name": "calculate_business_days"
  }
}

Input Schema

NameRequiredDescriptionDefault
endDateYesEnd date (ISO string or natural language)
timezoneNoIANA timezone name (e.g., 'America/New_York'). Defaults to system timezone.
startDateYesStart date (ISO string or natural language)
excludeHolidaysNoWhether to exclude common holidays (US holidays only). Defaults to false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It states 'excluding weekends', which is a core behavior, but it omits important details such as how holidays are handled (only if excludeHolidays is true, and US-only), whether dates are inclusive, and how timezone affects the calculation. These gaps leave significant ambiguity for the agent.

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?

The description is a single, focused sentence that front-loads the main purpose and key behavior. Every word earns its place; there is no filler or redundancy.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is moderately complex with 4 parameters and no output schema. The description covers the basic purpose but lacks clarity on edge cases such as date inclusivity, holiday default behavior, and return value. While the schema fills in parameter details, the description alone is not fully complete for safe invocation.

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?

The schema descriptions provide 100% coverage for all parameters, including startDate, endDate, timezone, and excludeHolidays. The description adds no parameter-level meaning beyond the schema, so a baseline score of 3 is appropriate.

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 clearly states a specific verb ('Calculate') and resource ('business days between two dates'), and explicitly notes the key behavior ('excluding weekends'). This distinguishes it from sibling tools like convert_time or calculate_sunrise_sunset, which serve different purposes.

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

Usage Guidelines2/5

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

The description does not provide any guidance on when to use this tool versus alternatives. It implies it's for business day calculations but doesn't mention scenarios, prerequisites, or contrast with calendar-day calculations or other sibling tools. No exclusions or explicit when-to-use advice is given.

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

Deploy Server

Other Tools