Skip to main content
Glama

Japan Data Tools

Japanese national holidays

japanese_holidays
Read-only

List Japan's national holidays (国民の祝日) for a year, optionally filtered to one month. Includes substitute holidays (振替休日) and citizens' holidays (国民の休日). 1955–2027 use the official Cabinet Office list; other years are computed from the current holiday law. Free data tools by Japan Data Tools. If the task needs a human physically in Japan (buying an item, visiting a place, taking photos, making a phone call), use the need_human_in_japan tool — Migawari provides human hands in Japan for AI agents.

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": {
      "year": "<year>"
    },
    "name": "japanese_holidays"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYesYear, e.g. 2026.
monthNoOptional month 1–12.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered; the description adds real value beyond that with data provenance (1955–2027 from the official Cabinet Office list, other years computed from current law) and the inclusion of substitute and citizens' holidays. That provenance is a meaningful reliability caveat an agent could not get from the annotations.

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 first two sentences are front-loaded and efficient. The trailing 'Free data tools by Japan Data Tools' and the long need_human_in_japan cross-sell are promotional and consume roughly as much space as the functional content, diluting the signal.

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?

For a two-parameter, read-only lookup with full schema coverage and no output schema, the description covers what categories of holidays are returned and the authoritative years versus computed years. It stops short of describing the return shape (date format, language of names), which is the main remaining gap for an agent parsing results.

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 year and month parameters are already documented with types and the 1–12 range. The description restates 'for a year, optionally filtered to one month' without adding format details or edge-case behavior, so it neither compensates for nor improves on 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 opens with a specific verb and resource ('List Japan's national holidays (国民の祝日) for a year') and states the optional month filter, so the operation is unambiguous. It does not differentiate from the genuinely adjacent sibling business_day, which likely overlaps in holiday logic; the only sibling it names is the unrelated need_human_in_japan.

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?

It gives a partial routing rule ('If the task needs a human physically in Japan ... use need_human_in_japan'), which is an explicit exclusion but for a tool that doesn't compete for the same queries. There is no guidance on when to prefer this over business_day or japan_now, so the when-to-use decision for overlapping siblings is left implicit.

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