Skip to main content
Glama

Japan Calendar

List Japanese holidays

list_holidays
Read-onlyIdempotent

List Japanese national holidays (including substitute holidays) between two dates, up to 5 years.

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": {
      "from": "<from>",
      "to": "<to>"
    },
    "name": "list_holidays"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesLast date, YYYY-MM-DD
fromYesFirst date, YYYY-MM-DD

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and closed-world, so the safety profile is covered. The description adds genuinely useful behavior beyond that: substitute holidays are included in results and the queryable window is limited to 5 years. It stops short of saying what happens when the range exceeds 5 years (error versus truncation).

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?

A single sentence that front-loads the resource and folds the two most decision-relevant qualifiers (substitute holidays, 5-year cap) into the same breath. Nothing is wasted or buried.

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?

For a simple two-parameter read tool with full annotation coverage, the description is nearly sufficient, but there is no output schema and the description never indicates the return shape (e.g., a list of dates with holiday names). An agent must guess what it gets back.

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% and both parameters (from, to) carry format and pattern constraints, so the schema does the heavy lifting. The description adds only that the interval is inclusive of a holiday span and is bounded at 5 years; it gives no additional per-parameter semantics, so baseline 3 applies.

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?

States a specific verb and resource ('List Japanese national holidays') plus two distinguishing scope details: substitute holidays are included and the range is capped at 5 years. It does not explicitly contrast with siblings, but none of the listed siblings (check_date, to_wareki, etc.) overlap with holiday retrieval, so ambiguity is low.

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 by the date-pair framing and the 'up to 5 years' constraint, which tells an agent when the call is valid. There is no explicit when-to-use/when-not guidance or named alternative for related date tasks (e.g., business-day counting belongs to siblings), so an agent must infer routing.

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.