Skip to main content
Glama

Argentina holidays and business days

ar_feriados
Read-onlyIdempotent

Argentine national holidays (feriados, incl. puentes turisticos) for a year, and optionally a date check: weekday, holiday name, is_business_day, next business day, and date + N business days (skips weekends and holidays). Send {} for this year, {year}, or {date, add_business_days}. Source failure = no charge. Paid tool: 0.002 USDC per call via x402 (USDC on Base, Polygon or Solana, no account or key). An unpaid call returns a payment-required result (isError, structuredContent with x402Version 2 and accepts); sign one of the accepts and retry the same call with the PaymentPayload in params._meta["x402/payment"]. Returns JSON text; the settlement is in result._meta["x402/payment-response"].

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
dateNoDate to check, YYYY-MM-DD
yearNoYear (default: current, or the year of date)
add_business_daysNoBusiness days to add to date

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/openWorld, but the description goes well beyond them: it discloses the x402 paid-call flow, the exact shape of an unpaid response (isError with structuredContent containing x402Version 2 and accepts), how to retry with PaymentPayload in params._meta, that source failure incurs no charge, and where settlement appears. For a metered third-party API this is exactly the context an agent needs before calling.

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?

Purpose and invocation modes are front-loaded in the first two sentences, which is the right ordering. The payment mechanics are dense and packed into one long block, but every sentence carries information the agent cannot get elsewhere; only minor tightening is possible.

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?

There is no output schema, and the description compensates by naming the returned fields (weekday, holiday name, is_business_day, next business day) plus the JSON-text return form and the payment-response location. Combined with the payment and retry semantics, nothing material is missing for correct invocation.

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?

Schema coverage is 100%, so baseline is 3; the description earns an extra point by explaining the coupling between parameters — that year is implied by date and that add_business_days is only meaningful alongside date. That mode-combination logic is not fully spelled out in the schema.

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?

States a specific resource (Argentine national holidays incl. puentes turisticos) and a specific secondary capability (date check returning weekday, holiday name, is_business_day, next business day, date + N business days). This is clearly distinguishable from all listed siblings (ar_cbu, ar_cuit, ar_dolar, ar_inflacion, ar_phone, fx_rate, etc.), none of which overlap.

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?

"Send {} for this year, {year}, or {date, add_business_days}" enumerates the three valid invocation shapes explicitly, which is unusually actionable guidance. It stops short of stating when not to use the tool or naming an alternative, but no sibling competes for this purpose.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources