Skip to main content
Glama

Caelara Labs Global Locale

public_holiday_lookup

Public holidays for a country and year, with an optional is-holiday check for one date

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_holiday_lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoOptional YYYY-MM-DD to test
yearNoYear (default current)
countryYesISO alpha-2 country code

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden, yet it says nothing about data source or coverage, error behavior for unknown country codes, or whether the date parameter changes the response shape (boolean check vs. holiday list). For a tool whose output form is the main behavioral question, this is a notable gap.

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?

A single front-loaded sentence with the resource stated first and the optional mode second. Nothing is wasted, though the phrasing around the is-holiday check is slightly compressed and could be clearer.

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?

The tool is simple, all three parameters are documented, and no output schema exists. However, because there is no output schema, the description should have stated what comes back in each mode; that omission leaves the definition merely adequate for a lookup with a branching response.

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 the baseline is 3. The description adds only marginal meaning, mainly that supplying date turns the call into an is-holiday test; year's default and country's ISO alpha-2 format are already fully documented in 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 names the resource (public holidays) and the scoping keys (country and year), plus an optional single-date check. That is specific enough to separate it from siblings such as vat_gst_rate_lookup or business_hours_calc, but it never names or contrasts an alternative explicitly.

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 alternatives. The only implied usage signal is that date is optional and drives an is-holiday check, which an agent could infer from the schema anyway.

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