ToolForte

Dutch Public Holidays

dutch_public_holidays

Read-onlyIdempotent

Exact Dutch public holidays for a year, including movable feasts (Easter, Ascension, Whitsun) and King's Day rules. Use this instead of computing Dutch holidays yourself.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`year`	Yes	Calendar year, 1900 to 2200

Output Schema

TableJSON Schema

Name	Required	Description
`year`	No
`result`	No	The result, when it is not an object
`holidays`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 13, 2026

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"

Changed2 schema fields changedSep 7, 2026

addedInput schema / properties / year / description
```
Added value: +"Calendar year, 1900 to 2200"
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": {},
+  "properties": {
+    "holidays": {
+      "items": {},
+      "type": "array"
+    },
+    "result": {
+      "description": "The result, when it is not an object"
+    },
+    "year": {
+      "type": "number"
+    }
+  },
+  "type": "object"
+}

Changed2 schema fields changedSep 7, 2026

removedInput schema / properties / year / description
```
Removed value: -"Calendar year, 1900 to 2200"
```

changedOutput schema / (root)

Previous value: -{
-  "$schema": "https://json-schema.org/draft/2020-12/schema",
-  "additionalProperties": {},
-  "properties": {
-    "holidays": {
-      "items": {},
-      "type": "array"
-    },
-    "result": {
-      "description": "The result, when it is not an object"
-    },
-    "year": {
-      "type": "number"
-    }
-  },
-  "type": "object"
-}New value: +null

Changed2 schema fields changedSep 5, 2026

addedInput schema / properties / year / description
```
Added value: +"Calendar year, 1900 to 2200"
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": {},
+  "properties": {
+    "holidays": {
+      "items": {},
+      "type": "array"
+    },
+    "result": {
+      "description": "The result, when it is not an object"
+    },
+    "year": {
+      "type": "number"
+    }
+  },
+  "type": "object"
+}

First observedSep 1, 2026

TDQS

A4.1/5.0

Behavior3/5

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

Annotations already declare the full safety profile (readOnly, idempotent, non-destructive, closed-world), and an output schema exists, so return values need not be described. The description adds only that results are 'exact' and lists the feast categories covered, which is modest added context beyond structured fields.

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 tight sentences with zero filler, and the scope/contents statement is front-loaded before the usage directive.

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

Completeness5/5

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

For a single-parameter lookup tool with an output schema and complete annotations, nothing an agent needs to invoke it correctly is missing. The description covers purpose, domain specifics, and when to prefer it.

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 single `year` parameter is fully documented with its 1900-2200 range in the schema. The description adds no syntax, format, or semantics beyond that, so the baseline 3 applies.

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 precise resource ('Exact Dutch public holidays for a year') and enriches it with the specific contents it returns (movable feasts, King's Day rules). An agent can immediately distinguish this domain-specific calculator from generic siblings like working_days_between or calculate_vat.

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?

Explicitly instructs the agent to use this rather than computing Dutch holidays itself, which is a genuine when-to-use directive. It offers no when-not guidance or named alternative tool, but for such a narrow tool that is a minor omission.

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

All ToolForte tools Inspect

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

Need Help?