Skip to main content
Glama

MCP Europe Tools

by app.railway.up.mcp-europe-tools-production
OverviewDiscussionsAdmin

get_portugal_holidays

Read-onlyIdempotent

Returns all Portuguese national public holidays for a given year as a structured list. Each holiday includes { date: 'YYYY-MM-DD', name: string, name_en: string }. Returns 10 mandatory national holidays defined by Portuguese law. Use when calculating business deadlines, delivery dates, payment due dates, SLA periods, or scheduling tasks that must avoid non-working days in Portugal. Does not include municipal or regional holidays (e.g. Lisbon June 13, Porto June 24) which vary by city.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
yearYesCalendar year as a 4-digit integer. Example: 2026

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedOutput schema / (root)
      Previous value: -{
-  "$schema": "http://json-schema.org/draft-07/schema#",
-  "additionalProperties": false,
-  "properties": {
-    "country": {
-      "type": "string"
-    },
-    "holidays": {
-      "items": {
-        "additionalProperties": false,
-        "properties": {
-          "date": {
-            "type": "string"
-          },
-          "name": {
-            "type": "string"
-          },
-          "name_en": {
-            "type": "string"
-          }
-        },
-        "required": [
-          "date",
-          "name",
-          "name_en"
-        ],
-        "type": "object"
-      },
-      "type": "array"
-    },
-    "total_holidays": {
-      "type": "number"
-    },
-    "year": {
-      "type": "number"
-    }
-  },
-  "required": [
-    "year",
-    "country",
-    "total_holidays",
-    "holidays"
-  ],
-  "type": "object"
-}New value: +null
  2. Changed2 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "country": {
+      "type": "string"
+    },
+    "holidays": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "date": {
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          },
+          "name_en": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "date",
+          "name",
+          "name_en"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total_holidays": {
+      "type": "number"
+    },
+    "year": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "year",
+    "country",
+    "total_holidays",
+    "holidays"
+  ],
+  "type": "object"
+}
  3. Changed1 schema field changed
    • changedInput schema / properties / year / description
      Previous value: -"The year to get holidays for. Example: 2026"New value: +"Calendar year as a 4-digit integer. Example: 2026"
  4. Changed1 schema field changed
    • changedInput schema / properties / year / description
      Previous value: -"The year to get holidays for (e.g. 2026)"New value: +"The year to get holidays for. Example: 2026"
  5. Changed1 schema field changed
    • changedInput schema / properties / year / description
      Previous value: -"The year to get holidays for (e.g. 2025)"New value: +"The year to get holidays for (e.g. 2026)"
  6. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations provide readOnlyHint and idempotentHint, and the description adds meaningful behavioral details: the exact output structure, the count (10 mandatory national holidays defined by law), and the exclusion of municipal/regional holidays. This goes beyond the annotation-only safety profile.

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?

Three sentences, front-loaded with purpose, then output structure, use cases, and exclusions. No unnecessary words; every sentence adds value.

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 simple tool with one parameter and no output schema, the description covers function, output format, scope, and limitations. An agent has enough context to decide when to use it and interpret results.

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 input schema fully documents the 'year' parameter with type and example, so description doesn't need to add more. The phrase 'for a given year' reinforces but doesn't extend schema information. Baseline 3 is appropriate given high schema coverage.

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 the tool 'Returns all Portuguese national public holidays for a given year as a structured list,' with specific verb and resource. It distinguishes from sibling country-holiday tools by explicitly naming Portugal and excluding municipal holidays.

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

Usage Guidelines5/5

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

Explicit usage context is provided: 'Use when calculating business deadlines, delivery dates, payment due dates, SLA periods, or scheduling tasks that must avoid non-working days in Portugal.' It also gives a clear exclusion ('Does not include municipal or regional holidays'), guiding agents away from inappropriate use.

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

All MCP Europe Tools toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources