Skip to main content
Glama
josemvelez78

mcp-europe-business

get_france_holidays

Read-onlyIdempotent

Retrieves all French national public holidays for a given year, with dynamic calculation of Easter-dependent holidays using the Anonymous Gregorian algorithm.

Instructions

Returns all French national public holidays for a given year. Easter-dependent holidays (Easter Monday, Ascension, Whit Monday) are dynamically calculated using the Anonymous Gregorian algorithm. Returns 11 mandatory holidays defined by French law.

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

  • The get_france_holidays tool handler function. It registers the tool with server.registerTool, receives a 'year' parameter, computes Easter-dependent holidays using the Anonymous Gregorian algorithm, and returns 11 French national holidays.
    // ── 6. Get France Holidays ──
    server.registerTool("get_france_holidays", {
      description: "Returns all French national public holidays for a given year. Easter-dependent holidays (Easter Monday, Ascension, Whit Monday) are dynamically calculated using the Anonymous Gregorian algorithm. Returns 11 mandatory holidays defined by French law.",
      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 France Public Holidays", readOnlyHint: true, idempotentHint: true, openWorldHint: false }
    }, async ({ year }) => {
      const a = year % 19, b = Math.floor(year / 100), c = year % 100;
      const d = Math.floor(b / 4), e = b % 4, f = Math.floor((b + 8) / 25);
      const g = Math.floor((b - f + 1) / 3), h = (19 * a + b - d - g + 15) % 30;
      const i = Math.floor(c / 4), k = c % 4, l = (32 + 2 * e + 2 * i - h - k) % 7;
      const m = Math.floor((a + 11 * h + 22 * l) / 451);
      const month = Math.floor((h + l - 7 * m + 114) / 31);
      const day = ((h + l - 7 * m + 114) % 31) + 1;
      const easter = new Date(year, month - 1, day);
      const addDays = (date, days) => { const d = new Date(date); d.setDate(d.getDate() + days); return d; };
      const fmt = (d) => d.toISOString().split("T")[0];
      const holidays = [
        { date: `${year}-01-01`, name: "Jour de l'An", name_en: "New Year's Day" },
        { date: fmt(addDays(easter, 1)), name: "Lundi de Pâques", name_en: "Easter Monday" },
        { date: `${year}-05-01`, name: "Fête du Travail", name_en: "Labour Day" },
        { date: `${year}-05-08`, name: "Victoire 1945", name_en: "Victory in Europe Day" },
        { date: fmt(addDays(easter, 39)), name: "Ascension", name_en: "Ascension Day" },
        { date: fmt(addDays(easter, 50)), name: "Lundi de Pentecôte", name_en: "Whit Monday" },
        { date: `${year}-07-14`, name: "Fête Nationale", name_en: "Bastille Day" },
        { date: `${year}-08-15`, name: "Assomption", name_en: "Assumption of Mary" },
        { date: `${year}-11-01`, name: "Toussaint", name_en: "All Saints Day" },
        { date: `${year}-11-11`, name: "Armistice", name_en: "Armistice Day" },
        { date: `${year}-12-25`, name: "Noël", name_en: "Christmas Day" },
      ];
      return { content: [{ type: "text", text: JSON.stringify({ year, country: "France", total_holidays: holidays.length, holidays }) }] };
    });
  • index.js:132-138 (registration)
    Registration of the get_france_holidays tool via server.registerTool, including description, input schema (year), output schema, and annotations.
    // ── 6. Get France Holidays ──
    server.registerTool("get_france_holidays", {
      description: "Returns all French national public holidays for a given year. Easter-dependent holidays (Easter Monday, Ascension, Whit Monday) are dynamically calculated using the Anonymous Gregorian algorithm. Returns 11 mandatory holidays defined by French law.",
      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 France Public Holidays", readOnlyHint: true, idempotentHint: true, openWorldHint: false }
    }, async ({ year }) => {
  • Input and output schemas for get_france_holidays: input expects a 4-digit year; output returns year, country, total_holidays, and an array of holidays with date, name, and name_en fields.
    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() })) },
Behavior4/5

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

Annotations already indicate readOnly and idempotent. Description adds context about algorithm (Anonymous Gregorian) and the exact number of holidays, which is beyond annotations.

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 short sentences, each informative. No unnecessary words or repetition.

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?

Description mentions return value (11 holidays) and algorithm. With output schema present, it provides sufficient context for a tool with a single parameter and predictable output.

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 covers 100% of parameters with a clear description for the single parameter year. Description does not add extra meaning beyond the schema, 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?

Description clearly states it returns all French national public holidays for a given year, specifying the number (11) and mentioning dynamic calculation for Easter-dependent holidays. This distinguishes it 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 indicates it is for French holidays in a given year. While no explicit when-not-to-use or alternatives are provided, the sibling tools for other countries implicitly guide selection.

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