Public Holidays & Business Days (200+ countries)

business_days

Work out a payment, delivery or legal deadline in business days for a given country. Lists a year's public holidays for 200+ countries and their regions, checks whether a date is a business day, adds or subtracts N business days, or counts business days between two dates, with configurable weekend days. Use when a due date or notice period depends on local public holidays. $0.002 per call, USDC on Base (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": "business_days"
  }
}

Input Schema

Name	Required	Description
`add`	No	Business days to add (negative to subtract)
`date`	No	Start date YYYY-MM-DD (default today)
`year`	No	Year to list all public holidays
`until`	No	End date YYYY-MM-DD to count business days between
`region`	No	Optional state/region code, e.g. BY
`country`	No	ISO2 country, e.g. DE
`weekend`	No	Weekend days as numbers 0-6 (0=Sunday), default 0,6
`payment_signature`	No	x402 v2 PAYMENT-SIGNATURE header value. Omit to receive payment requirements.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 16, 2026

TDQS

A4.1/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does disclose non-obvious operational facts: coverage (200+ countries and regions), configurable weekend days, and the x402 payment model with a stated price of $0.002 per call in USDC on Base. It omits failure behavior, rate limits, or what happens with an unpayable/unpaid request.

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?

Front-loaded with the core purpose, then the operation list, then the usage cue and pricing. Every sentence carries information; the operation enumeration is dense but not padded.

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?

No output schema and no annotations, so the description must cover behavior and it does reasonably: scope, modes, weekend configurability, and cost model. It is a bit thin on the payment step (the mechanics live in the payment_signature schema field) and on return shapes.

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%, so every parameter is already documented in the schema, establishing a baseline of 3. The description adds mode-level meaning (negative values subtract, weekend is configurable) but no syntax or format detail beyond what the schema provides.

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?

The description names a concrete resource (business-day deadlines / public holidays) and enumerates the exact operations supported: list holidays, check a date, add/subtract N days, count between dates. An agent knows precisely what class of computation this tool performs, including the 200+ country and region scope.

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?

"Use when a due date or notice period depends on local public holidays" gives explicit triggering context. There are no sibling tools to route against, so the lack of alternatives/exclusions is acceptable, but the description does not say which mode to prefer for a given input combination.

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

All Public Holidays & Business Days (200+ countries) 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?