Agent Tools

public_holidays

Public holiday calendar and list for 100+ countries by year. For scheduling, payroll and delivery planning. Returns national holidays with dates and names. Source: Nager.Date API. Price $0.001 USDC per call via x402. Example output: {"year":2027,"country":"US","holidays":[{"date":"2027-01-01","name":"New Year's Day","local_name":"New Year's Day","global":true}]}

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

Input Schema

Name	Required	Description	Default
`year`	Yes	Year, e.g. 2027
`country`	Yes	ISO 3166 alpha-2

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 22, 2026

TDQS

A3.9/5.0

Behavior4/5

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses the source API, per-call price via x402, and return shape with an example output, though it omits rate limits and error behavior.

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 definition is front-loaded with purpose and use cases, followed by relevant source, price, and output example. The phrase 'calendar and list' is slightly redundant, and the example output lengthens the description, but no sentence is clearly wasteful.

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?

For a simple two-required-parameter lookup tool with no output schema, the description supplies purpose, use contexts, source, cost, and an example return value—enough to invoke it correctly. It does not address alternatives or edge cases, but the core call context is complete.

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%, and the schema already documents country as ISO 3166 alpha-2 and year with an example. The description adds only that coverage spans 100+ countries and shows example values, offering little additional parameter meaning beyond the schema.

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 clearly states that the tool returns a public holiday calendar/list for 100+ countries by year, so the resource and scope are specific. It does not explicitly distinguish itself from related siblings like business_days or business_day_add.

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?

It provides clear use contexts—scheduling, payroll, and delivery planning—which helps an agent understand when the tool is relevant. However, it gives no explicit when-not conditions or alternatives such as business-day calculation tools.

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

All Agent Tools 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?