Skip to main content

toolforte

by io.github.Toinedotcom

Overview Discussions Admin

Dutch Public Holidays

dutch_public_holidays

Read-onlyIdempotent

Use this when you need the dates of the Dutch public holidays in a given year. Example prompt: "When is Ascension Day in the Netherlands in 2027?" 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. Costs 1 credit. The answer is deterministic.

Input Schema

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

Output Schema

Name	Required	Description	Default
`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 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.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and openWorldHint=false, so safety is covered. The description adds genuinely non-derived context: the result is deterministic, it costs 1 credit, and it handles movable feasts and King's Day rules — the last being the main edge-case an agent would worry about.

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?

Short and front-loaded with the primary use case in the first sentence. Some redundancy and fragment-style sentences ('Costs 1 credit. The answer is deterministic.') keep it from a perfect score, but every line carries information.

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?

An output schema exists, so return values need no explanation. With scope, edge cases, determinism, and cost all stated, an agent has everything required to call this correctly.

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?

There is a single parameter with 100% schema coverage including the 1900–2200 range, so the schema does the explaining. The description only restates 'in a given year' and adds nothing about boundaries or format, so 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 specific verb ('need the dates of') plus a precise resource ('Dutch public holidays in a given year') and even enumerates the tricky cases covered (movable feasts, King's Day rules). An agent can immediately tell this is a lookup tool for a fixed jurisdiction, distinct from siblings like working_days_between.

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 says when to use it ('when you need the dates... in a given year') and supplies a concrete example prompt, plus a strong negative guideline ('use this instead of computing Dutch holidays yourself'). It does not name a sibling tool or state exclusions versus working_days_between, so it falls short of a 5.

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

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?