Skip to main content
Glama
0xKoller

MCP Argentina Datos

by 0xKoller

get-feriados

Retrieve Argentina's official holidays for the current year. Use this tool to access national holiday dates through the Argentina Datos API.

Instructions

Devuelve los feriados del año

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • main.ts:110-137 (handler)
    Handler function for 'get-feriados' tool, calls getFeriados() and returns JSON response or error.
    server.tool("get-feriados", "Devuelve los feriados del año", {}, async ({}) => {
      try {
        const data = await getFeriados();
        if (data.length === 0) {
          return {
            content: [
              {
                type: "text",
                text: "No se encontraron feriados para el año actual",
              },
            ],
          };
        }
        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" }],
        };
      }
    });
  • main.ts:26-29 (schema)
    Schema definition for 'get-feriados' tool in the MCP server tools list (empty parameters).
      name: "get-feriados",
      description: "Devuelve los feriados del año",
      parameters: {},
    },
  • main.ts:110-137 (registration)
    Registration of the 'get-feriados' tool using server.tool, including inline handler.
    server.tool("get-feriados", "Devuelve los feriados del año", {}, async ({}) => {
      try {
        const data = await getFeriados();
        if (data.length === 0) {
          return {
            content: [
              {
                type: "text",
                text: "No se encontraron feriados para el año actual",
              },
            ],
          };
        }
        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 implementation of getFeriados helper function that fetches holidays data from API for given or current year.
    const BASE_URL = "https://api.argentinadatos.com/v1";
    export const getFeriados = async (year = new Date().getFullYear()) => {
      const feriados = await fetch(`${BASE_URL}/feriados/${year}`);
      const data = await feriados.json();
      return data;
    };
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states the tool returns holidays but doesn't disclose behavioral traits like whether it's read-only, requires authentication, has rate limits, returns structured data, or handles errors. For a tool with no annotation coverage, this is a significant gap in transparency.

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 in Spanish that directly states the tool's function. It's appropriately sized and front-loaded with the core purpose, with no wasted words or unnecessary elaboration.

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

Completeness3/5

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

Given the tool's simplicity (0 parameters, no output schema, no annotations), the description is minimally adequate but incomplete. It states what the tool does but lacks behavioral context, output details, or usage guidance. For a tool with no structured metadata, the description should do more to compensate, but it meets the bare minimum.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has 0 parameters with 100% schema description coverage, so the schema fully documents the absence of inputs. The description doesn't need to add parameter semantics, and it correctly implies no parameters are needed by stating it returns holidays for the year without mentioning inputs. Baseline 4 is appropriate for zero-parameter tools.

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 'Devuelve los feriados del año' clearly states the verb ('devuelve' - returns) and resource ('feriados del año' - holidays of the year). It's specific about what the tool does, though it doesn't explicitly differentiate from its sibling 'get-feriados-timeframe' beyond the implied scope difference (year vs timeframe).

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. While the name suggests it returns holidays for a year, there's no explicit comparison with 'get-feriados-timeframe' or indication of prerequisites. The description assumes usage context without stating it.

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