Skip to main content
Glama

Tax Compass — Japan tax rules by date

日本の祝日・休日(内閣府のデータ)

jp_holidays
Read-onlyIdempotent

List Japanese national holidays (国民の祝日) and official substitute/citizens' holidays (振替休日・国民の休日, shown as 「休日」) between two dates, or check one date, using the Cabinet Office (内閣府) official CSV. The dates come from the published CSV only, including 春分の日/秋分の日, substitute holidays and one-off holidays. Give either date, or from and to (at most 1,100 days apart). Returns an error for dates outside the published data (currently 1955-01-01 to 2027-12-31) instead of guessing.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "jp_holidays"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNo一覧の終わり(YYYY-MM-DD)
dateNo1日だけ確かめる時(YYYY-MM-DD)
fromNo一覧の始め(YYYY-MM-DD)

Output Schema

NameRequiredDescriptionDefault
notesYesこの答えに効いた決まり・前提(日本語)
resultYes
doc_urlYes人が読む説明のページ(式・出所・例)。利用者に次に読んでもらう先
sourcesYes
law_as_ofNo出所が書く法令の基準日(例:2026-04-01=令和8年4月1日現在法令等)
checked_onYesCyclix Agents が出所を最後に確かめた日
disclaimerYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real value beyond that: provenance (published CSV only, no computation), inclusion of 春分の日/秋分の日 and one-off holidays, and explicit error behavior outside 1955-01-01 to 2027-12-31 instead of guessing. It does not discuss pagination or response size, which keeps it from 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?

Three sentences, front-loaded with the core verb and resource, followed by mode selection, then the failure boundary. Every clause carries operational information — no restatement of the title or filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 values need not be described, and annotations cover safety and idempotency. Combined with fully documented parameters, source provenance, date-range limits and error behavior, nothing an agent needs to call this correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds semantics the schema does not encode: `date` and `from`/`to` are alternative modes rather than freely combinable, and the range is capped at 1,100 days. That meaningfully constrains how the three string parameters should be 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?

States a specific verb and resource — 'List Japanese national holidays (国民の祝日) and official substitute/citizens' holidays' — plus the second mode 'check one date', and names the authoritative source (Cabinet Office CSV). An agent can immediately tell this is the holiday-calendar tool rather than the business-day or era-conversion siblings.

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?

Clearly describes the two invocation modes ('between two dates, or check one date') and the hard constraint of at most 1,100 days apart, which tells the agent how to frame a request. It stops short of explicitly naming an alternative tool or stating when NOT to use it (e.g., for counting business days), so it is clear context without exclusions.

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