Skip to main content
Glama
josemvelez78

mcp-europe-business

get_portugal_holidays

Read-onlyIdempotent

Retrieve Portuguese national public holidays for any year to plan business deadlines, delivery dates, payment due dates, and SLA periods, avoiding non-working days.

Instructions

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.

Input Schema

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

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
yearYes
countryYes
total_holidaysYes
holidaysYes

Implementation Reference

  • index.js:89-109 (registration)
    Tool registration for 'get_portugal_holidays' via server.registerTool() including description, input/output schemas, and annotations.
    // ── 4. Get Portugal Holidays ──
    server.registerTool("get_portugal_holidays", {
      description: "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.",
      inputSchema: { year: z.number().describe("Calendar year as a 4-digit integer. Example: 2026") },
      outputSchema: { year: z.number(), country: z.string(), total_holidays: z.number(), holidays: z.array(z.object({ date: z.string(), name: z.string(), name_en: z.string() })) },
          annotations: { title: "Get Portugal Public Holidays", readOnlyHint: true, idempotentHint: true, openWorldHint: false }
    }, async ({ year }) => {
      const holidays = [
        { date: `${year}-01-01`, name: "Ano Novo", name_en: "New Year's Day" },
        { date: `${year}-04-25`, name: "Dia da Liberdade", name_en: "Freedom Day" },
        { date: `${year}-05-01`, name: "Dia do Trabalhador", name_en: "Labour Day" },
        { date: `${year}-06-10`, name: "Dia de Portugal", name_en: "Portugal Day" },
        { date: `${year}-08-15`, name: "Assunção de Nossa Senhora", name_en: "Assumption of Mary" },
        { date: `${year}-10-05`, name: "Implantação da República", name_en: "Republic Day" },
        { date: `${year}-11-01`, name: "Dia de Todos os Santos", name_en: "All Saints Day" },
        { date: `${year}-12-01`, name: "Restauração da Independência", name_en: "Independence Restoration Day" },
        { date: `${year}-12-08`, name: "Imaculada Conceição", name_en: "Immaculate Conception" },
        { date: `${year}-12-25`, name: "Natal", name_en: "Christmas Day" },
      ];
      return { content: [{ type: "text", text: JSON.stringify({ year, country: "Portugal", total_holidays: holidays.length, holidays }) }] };
    });
  • index.js:95-109 (handler)
    Handler function for get_portugal_holidays that returns 10 fixed-date Portuguese national holidays for a given year as structured data.
    }, async ({ year }) => {
      const holidays = [
        { date: `${year}-01-01`, name: "Ano Novo", name_en: "New Year's Day" },
        { date: `${year}-04-25`, name: "Dia da Liberdade", name_en: "Freedom Day" },
        { date: `${year}-05-01`, name: "Dia do Trabalhador", name_en: "Labour Day" },
        { date: `${year}-06-10`, name: "Dia de Portugal", name_en: "Portugal Day" },
        { date: `${year}-08-15`, name: "Assunção de Nossa Senhora", name_en: "Assumption of Mary" },
        { date: `${year}-10-05`, name: "Implantação da República", name_en: "Republic Day" },
        { date: `${year}-11-01`, name: "Dia de Todos os Santos", name_en: "All Saints Day" },
        { date: `${year}-12-01`, name: "Restauração da Independência", name_en: "Independence Restoration Day" },
        { date: `${year}-12-08`, name: "Imaculada Conceição", name_en: "Immaculate Conception" },
        { date: `${year}-12-25`, name: "Natal", name_en: "Christmas Day" },
      ];
      return { content: [{ type: "text", text: JSON.stringify({ year, country: "Portugal", total_holidays: holidays.length, holidays }) }] };
    });
  • Input schema (Zod) requiring a 'year' number parameter for the get_portugal_holidays tool.
    inputSchema: { year: z.number().describe("Calendar year as a 4-digit integer. Example: 2026") },
    outputSchema: { year: z.number(), country: z.string(), total_holidays: z.number(), holidays: z.array(z.object({ date: z.string(), name: z.string(), name_en: z.string() })) },
  • Output schema (Zod) specifying the structure: year, country, total_holidays, and array of holiday objects with date, name, name_en.
    outputSchema: { year: z.number(), country: z.string(), total_holidays: z.number(), holidays: z.array(z.object({ date: z.string(), name: z.string(), name_en: z.string() })) },
Behavior4/5

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

Annotations already indicate read-only and idempotent. The description adds that it returns exactly 10 mandatory holidays defined by law, with date, name, and English name fields. No contradictions.

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: first states purpose and output format, second lists use cases. No wasted words, front-loaded.

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 one-parameter tool with output schema and clear annotations, the description covers purpose, output structure, and usage context completely.

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 single parameter 'year' is fully described in the schema (100% coverage). The description does not add extra parameter details beyond that, so 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?

The description clearly states the tool returns Portuguese national public holidays for a given year as a structured list, specifying the resource, action, and input. It distinguishes from sibling tools for other countries.

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?

The description provides explicit use cases like business deadlines, delivery dates, and SLA periods. It does not include when-not-to-use or alternative tools, but the context is clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/josemvelez78/mcp-europe-business'

If you have feedback or need assistance with the MCP directory API, please join our Discord server