Crypto, web, finance and app data tools

Public Holidays

public_holidays

Public holidays of 150+ countries and their states/regions, or stock-market holidays (NYSE, ECB TARGET), for any year, and whether a given date is a holiday or business day with the next business day. Use for scheduling, delivery dates, payroll or market-open checks.

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

Input Schema

Name	Required	Description	Default
`date`	No
`year`	No
`country`	Yes
`subdivision`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 22, 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 burden and does disclose meaningful behavior: two distinct calendar families (national/subdivision vs. exchange calendars such as NYSE and ECB TARGET), a date-check mode that also returns the next business day, and arbitrary-year support. It does not state error behavior for unknown countries or subdivision naming conventions, which keeps it below a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One dense sentence establishes capability and scope, and a short second sentence gives usage contexts. It is front-loaded with what the tool returns and wastes no words despite covering a lot of ground.

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?

An output schema exists, so return-value description is unnecessary, and the capability surface is well covered. However, for a tool whose correctness hinges on input formats (country/subdivision identifiers, date representation) and on the interaction between the optional year and date arguments, the description leaves the agent guessing, which is a real gap given 0% schema coverage.

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 0%, so the description must compensate. It implicitly touches all four parameters — country, subdivision ("states/regions"), year ("for any year"), and date ("whether a given date is a holiday") — but adds no format guidance such as ISO country codes, date string syntax, or what happens when both year and date are supplied.

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 the resource (public holidays / stock-market holidays), the coverage (150+ countries plus states/regions, NYSE and ECB TARGET calendars), and the two query modes (holiday lists for a year, or a holiday/business-day check for a date). No sibling tool overlaps this domain, so no differentiation is needed and the purpose is unambiguous.

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 for scheduling, delivery dates, payroll or market-open checks" gives concrete use contexts that let an agent decide to reach for it. It stops short of exclusions or stating alternatives (e.g., when to prefer a plain date library or a time-zone tool), so it is clear context rather than full routing guidance.

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

All Crypto, web, finance and app data 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?