Datos UY/AR

Feriados de Argentina

ar_feriados

Feriados nacionales de Argentina por año desde la fuente oficial (argentina.gob.ar). Años disponibles: 2025, 2026. Tipos: inamovible, trasladable, no_laborable, turistico, especial.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "anio": "<anio>"
    },
    "name": "ar_feriados"
  }
}

Input Schema

Name	Required	Description	Default
`mes`	No
`anio`	Yes
`tipo`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 7, 2026

TDQS

B3.2/5.0

Behavior3/5

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

No annotations exist, so the description carries the full burden. It usefully discloses the official data source and the bounded set of supported years, but says nothing about return format, ordering, caching, or how filtered results behave when no holiday matches.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences with no filler, front-loading the resource and its scope. The available-years constraint follows immediately, so the most actionable detail appears early.

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?

For a simple 3-param lookup tool with no output schema or annotations, it covers source, year range, and type vocabulary. The omission of mes semantics and any description of the returned holiday records leaves gaps an agent must infer.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate for all three parameters. It clarifies anio (years 2025/2026) and restates the tipo enum values, but the mes parameter is never mentioned and no format/semantics are given beyond the schema's numeric bounds.

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 states a specific verb/resource: national Argentine holidays by year, sourced from the official argentina.gob.ar site. It is clearly distinguishable in intent from sibling ar_feriado_proximo (next holiday), though it never names that sibling explicitly.

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

Usage Guidelines3/5

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

It discloses hard usage constraints — only years 2025 and 2026 are available — which tells the agent when the call will succeed. However, it gives no explicit when-to-use/when-not guidance or routing to the 'proximo' sibling for upcoming-holiday queries.

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

All Datos UY/AR tools Inspect

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

Need Help?