Skip to main content
Glama
Sign In

APIVerve

by com.apiverve
OverviewDiscussionsAdmin

World Holidays

WorldHolidays
Read-only

World Holidays: World Holidays lists public holidays and observances for any two-letter country code, optionally for a state or region. It returns holiday dates, local and English names, day of week, event types and substitute-day flags, and can check whether a single date is a holiday. (Cost: 2 credits)

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

Input Schema

NameRequiredDescriptionDefault
dateNoCheck a single date (YYYY-MM-DD); returns isHoliday and only the holidays on that day. Overrides year
typeNoOnly return these holiday types, comma-separated: public, bank, school, optional, observance
yearNoThe year for which you want to get the holidays
regionNoState or region code (e.g. BY, CA or US-CA) to include regional holidays
countryYesThe 2-letter country code for which you want to get the holidays

Output Schema

NameRequiredDescriptionDefault
dataNo
errorNoError message, null on success
statusNo"ok" on success

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint and destructiveHint=false, so safety is covered. The description adds genuinely new context in the 2-credit cost, but its recap of return fields (dates, names, day of week, substitute flags) largely duplicates the existing output schema, and it says nothing about data source reliability or rate limits.

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

Conciseness3/5

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

The core two sentences are dense and front-loaded with the main capability, but the tautological title prefix wastes the most prominent position, and the trailing credit cost is a parenthetical afterthought rather than integrated into the guidance.

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 five well-described parameters, an output schema and read-only annotations, the definition covers what an agent needs to call it correctly and even discloses the credit cost. Minor gaps remain around rate limits and how regional codes interact with the year, but nothing essential is missing.

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 all five parameters are already documented, including the date-overrides-year rule and the type filter list. The description restates country/region/date semantics at a high level and adds nothing about the 'type' filter or the year default, so baseline 3 is 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?

The description gives a specific verb and resource ('lists public holidays and observances'), states the scope (two-letter country code, optional region) and a second mode (single-date holiday check). The only weakness is the redundant 'World Holidays: World Holidays' opener, which merely restates the name, and the absence of explicit differentiation from nearby siblings such as WorkingDays or LiturgicalCalendar.

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?

Usage is implied rather than prescribed: supplying a country code (plus optional region) selects the list mode, and supplying 'date' selects the single-day check. No when-not-to-use guidance or named alternatives are given, so the agent must infer that WorkingDays or LiturgicalCalendar serve related but different needs.

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

All APIVerve toolsInspect
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