Skip to main content
Glama

Paid public-data feeds (x402, 0.002 USD)

Public holidays for a country and year in one call: date, name, local name, type (country=US, year=2026)

holidays
Read-onlyIdempotent

Public holidays for a country and year in one call: date, name, local name, type (country=US, year=2026). For scheduling and calendar agents. Pay per call $0.002 USDC on Base via x402.

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": "holidays"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearNodefault current year
countryNo2-letter code, default US
x_paymentNosigned x402 payment (X-PAYMENT header value); omit on the first call to receive the price and payment requirements

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds genuinely new operational context that annotations cannot express: it is a paid endpoint at $0.002 USDC on Base via x402, and the schema's x_payment note explains the first call returns pricing before payment. It does not mention rate limits or result-set size, but the paid-invocation model is a substantive disclosure.

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 short sentences, front-loaded with what the tool returns, followed by audience and cost. Nothing is padded, though the first clause largely duplicates the title and the pricing sentence is packed in rather than separated.

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 three-optional-parameter read tool with no output schema and full schema coverage, the definition covers purpose, audience, and payment mechanics. What is thin is the return contract: it lists field names but not ordering, whether the list spans the whole year, or what an empty/invalid country code yields, which matters since there is no output schema to fall back on.

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 coverage is 100%, so defaults for year and country and the x_payment handshake are already documented in the schema. The description only restates example values (country=US, year=2026) already implied by the schema defaults, adding no format or edge-case meaning. Baseline 3 applies.

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 names the exact resource and scope (public holidays for a given country and year) and enumerates the returned fields (date, name, local name, type) with a concrete example. It lacks an explicit verb and never names a sibling, but no sibling in the catalog overlaps this domain, so the resource identification is sufficient for selection.

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?

"For scheduling and calendar agents" gives a usage context, which implies when the tool is appropriate. There is no when-not guidance, no mention of alternatives, and no explicit statement that year/country are optional and fall back to current-year/US defaults, leaving the agent to infer the trigger conditions.

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