Skip to main content
Glama
0xKoller

MCP Argentina Datos

by 0xKoller

get-feriados-timeframe

Retrieve official holidays for a specific year in Argentina to plan schedules, avoid conflicts, and ensure compliance with national observances.

Instructions

Devuelve los feriados de un año específico pasado por parámetro

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
yearYesEJ: 2025

Implementation Reference

  • main.ts:140-184 (handler)
    Handler implementation for the 'get-feriados-timeframe' tool. It takes a 'year' parameter, calls the helper getFeriados(year), handles errors, and returns JSON data or error messages.
    server.tool(
      "get-feriados-timeframe",
      "Devuelve los feriados de un año específico pasado por parámetro",
      {
        year: z.number().describe("EJ: 2025"),
      },
      async ({ year }) => {
        if (year === undefined) {
          return {
            content: [
              {
                type: "text",
                text: "No se ha provisto el parámetro 'year'",
              },
            ],
          };
        }
        try {
          const data = await getFeriados(year);
          if (data.length === 0) {
            return {
              content: [
                {
                  type: "text",
                  text: "No se encontraron feriados para el año especificado",
                },
              ],
            };
          }
          return {
            content: [
              {
                type: "text",
                text: JSON.stringify(data, null, 2),
                mimeType: "application/json",
              },
            ],
          };
        } catch (error) {
          return {
            content: [{ type: "text", text: "Error al obtener los feriados" }],
          };
        }
      }
    );
  • Core helper function getFeriados that performs the API fetch for feriados (holidays) data for a given year from argentinadatos.com API.
    export const getFeriados = async (year = new Date().getFullYear()) => {
      const feriados = await fetch(`${BASE_URL}/feriados/${year}`);
      const data = await feriados.json();
      return data;
    };
  • main.ts:30-36 (schema)
    Schema definition for the tool in the server's tools list, declaring name, description, and input parameters.
    {
      name: "get-feriados-timeframe",
      description: "Devuelve los feriados del año",
      parameters: {
        year: z.number().describe("EJ: 2025"),
      },
    },
  • main.ts:141-145 (registration)
    Tool registration call with name, description, and Zod schema for input validation within the server.tool method.
    "get-feriados-timeframe",
    "Devuelve los feriados de un año específico pasado por parámetro",
    {
      year: z.number().describe("EJ: 2025"),
    },
  • BASE_URL constant used by getFeriados to construct the API endpoint.
    const BASE_URL = "https://api.argentinadatos.com/v1";
Behavior2/5

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

With no annotations provided, the description carries full burden but offers minimal behavioral context. It doesn't disclose whether this is a read-only operation, what format the holidays are returned in, whether there are rate limits, or what happens with invalid years. 'Devuelve' implies a query operation but lacks operational details.

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?

The description is a single, efficient sentence that directly states the tool's function with zero wasted words. It's appropriately sized for a simple parameterized query tool.

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

Completeness2/5

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

For a query tool with no annotations and no output schema, the description is insufficient. It doesn't explain what format the holidays are returned in (dates, names, types), whether the year parameter has constraints, or what happens with edge cases. The description alone doesn't provide enough context for reliable tool invocation.

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% with the parameter 'year' well-documented in the schema. The description adds that it's for 'un año específico' (a specific year) which aligns with but doesn't significantly expand beyond the schema's 'EJ: 2025' example. Baseline 3 is appropriate when schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb ('Devuelve' - returns) and resource ('feriados' - holidays) with a specific scope ('de un año específico' - for a specific year). It distinguishes from the sibling 'get-feriados' by specifying the timeframe parameter requirement, though not explicitly contrasting functionality.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives like 'get-feriados' or other date-related tools. The description only states what it does, not when it's appropriate or what prerequisites exist.

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/0xKoller/mcp-argentina-datos'

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