Skip to main content
Glama

holidays

Read-only

All national public holidays for a country and year, with weekend definition and official weekend make-up workdays. Price: $0.002 USDC per request (fixed; one paid HTTP GET = one charge; x402 exact on Base or MPP on Tempo; 4xx errors are not charged).

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": {
      "country": "<country>",
      "year": "<year>"
    },
    "name": "holidays"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYesYYYY
countryYesISO alpha-2

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations cover the safety profile (readOnlyHint=true, openWorldHint=false), and the description adds context annotations cannot: the request is paid ($0.002 USDC fixed), one HTTP GET equals one charge, payment rails are x402/Base or MPP/Tempo, and 4xx errors are not billed. That billing detail materially affects whether an agent should call it.

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?

The core purpose is front-loaded in the first clause, with the pricing contract appended as a secondary sentence. The pricing parenthetical is dense but every clause (fixed price, per-request charge, payment rails, 4xx free) carries operational meaning.

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

Completeness4/5

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

With no output schema, the description still gives a partial picture of the return content ('weekend definition and official weekend make-up workdays'), and it fully covers the cost model. Only the exact response shape/field names are left unspecified, which is a minor gap.

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% ('year: YYYY', 'country: ISO alpha-2'), so the schema already carries both parameters fully. The description only restates 'country and year' without adding format or edge-case semantics, making the baseline 3 appropriate.

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?

States a specific verb-and-resource combination: 'All national public holidays for a country and year,' plus extra fields (weekend definition, make-up workdays). It is clearly about holidays rather than business-day arithmetic, though it never names the sibling tools to sharpen that partition.

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?

There is no when-to-use or when-not-to-use guidance and no mention of the business_day/business_days_* siblings, so an agent must infer from the resource name alone whether to pick this or a business-day counting tool.

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