Skip to main content
Glama

ToolForte

by com.toolforte
OverviewDiscussionsAdmin

Working Days Calculator

working_days_between
Read-onlyIdempotent

Count working days (Mon-Fri) between two dates inclusive, optionally excluding Dutch public holidays. Exact date math for SLA, payroll, and planning questions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
endYesYYYY-MM-DD
startYesYYYY-MM-DD
excludeDutchHolidaysNoSkip Dutch public holidays that fall on a weekday (default true)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
endNo
startNo
resultNoThe result, when it is not an object
totalDaysNo
weekendDaysNo
workingDaysNo
holidaysExcludedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • removedOutput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
  2. Changed2 schema fields changed
    • addedInput schema / properties / excludeDutchHolidays / description
      Added value: +"Skip Dutch public holidays that fall on a weekday (default true)"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": {},
+  "properties": {
+    "end": {
+      "type": "string"
+    },
+    "holidaysExcluded": {
+      "items": {},
+      "type": "array"
+    },
+    "result": {
+      "description": "The result, when it is not an object"
+    },
+    "start": {
+      "type": "string"
+    },
+    "totalDays": {
+      "type": "number"
+    },
+    "weekendDays": {
+      "type": "number"
+    },
+    "workingDays": {
+      "type": "number"
+    }
+  },
+  "type": "object"
+}
  3. Changed2 schema fields changed
    • removedInput schema / properties / excludeDutchHolidays / description
      Removed value: -"Skip Dutch public holidays that fall on a weekday (default true)"
    • changedOutput schema / (root)
      Previous value: -{
-  "$schema": "https://json-schema.org/draft/2020-12/schema",
-  "additionalProperties": {},
-  "properties": {
-    "end": {
-      "type": "string"
-    },
-    "holidaysExcluded": {
-      "items": {},
-      "type": "array"
-    },
-    "result": {
-      "description": "The result, when it is not an object"
-    },
-    "start": {
-      "type": "string"
-    },
-    "totalDays": {
-      "type": "number"
-    },
-    "weekendDays": {
-      "type": "number"
-    },
-    "workingDays": {
-      "type": "number"
-    }
-  },
-  "type": "object"
-}New value: +null
  4. Changed2 schema fields changed
    • addedInput schema / properties / excludeDutchHolidays / description
      Added value: +"Skip Dutch public holidays that fall on a weekday (default true)"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": {},
+  "properties": {
+    "end": {
+      "type": "string"
+    },
+    "holidaysExcluded": {
+      "items": {},
+      "type": "array"
+    },
+    "result": {
+      "description": "The result, when it is not an object"
+    },
+    "start": {
+      "type": "string"
+    },
+    "totalDays": {
+      "type": "number"
+    },
+    "weekendDays": {
+      "type": "number"
+    },
+    "workingDays": {
+      "type": "number"
+    }
+  },
+  "type": "object"
+}
  5. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so safety is covered. The description adds genuine behavioral semantics beyond that: Mon-Fri counting, inclusive bounds, and that holidays are optional. It does not mention edge cases (start > end, weekend-only ranges), so it stops short of full transparency.

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?

Two sentences, zero filler, with the counting rule front-loaded ahead of the use-case examples. Every clause carries information.

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?

An output schema exists, so return values need no explanation, and all three parameters are documented in the schema. The description supplies purpose, counting semantics, and use cases, leaving only minor edge-case behavior unstated.

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%, and the schema already documents the YYYY-MM-DD pattern and the excludeDutchHolidays default. The description restates rather than extends this, adding only the implicit point that weekends are excluded regardless of the flag. Baseline 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?

States a specific verb+resource (count working days between two dates) plus the exact counting rule (Mon-Fri, inclusive) and an optional modifier. An agent can distinguish it from dutch_public_holidays (which lists holidays) without opening either schema.

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?

"Exact date math for SLA, payroll, and planning questions" gives clear usage context. However, it never states when NOT to use it or names the sibling dutch_public_holidays as the alternative when the raw holiday list is what's wanted.

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

All ToolForte toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources