Skip to main content
Glama

Japan Calendar

Check a date in Japan

check_date
Read-onlyIdempotent

Tell whether a date is a Japanese national holiday, a weekend, or a business day, with the holiday name (Japanese and English) and the wareki 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": {
      "date": "<date>"
    },
    "name": "check_date"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesDate to check, YYYY-MM-DD
year_end_breakNoAlso treat Dec 31 - Jan 3 as non-business days (common for banks and most Japanese companies). Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered. The description adds real behavioral value by disclosing what comes back (classification plus holiday name in Japanese and English plus the wareki date), which matters because there is no output schema. It does not state edge behavior such as unsupported date ranges or what happens on invalid input, keeping it short of 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?

A single front-loaded sentence with no filler. The classification is stated first and the returned extras follow, which is the right ordering for an agent scanning the definition.

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 no output schema, the description covers purpose and return content, which is what an agent needs to call it correctly. Minor incompleteness remains around the year_end_break option's effect on the verdict and around supported date ranges, though the schema carries the former.

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 both 'date' (with its YYYY-MM-DD pattern) and 'year_end_break' are fully documented in the schema. The description adds no meaning beyond that and never mentions the year_end_break toggle, so the baseline of 3 applies.

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 ('Tell whether a date is a Japanese national holiday, a weekend, or a business day') and enumerates the outputs it returns, including the holiday name in both languages and the wareki date. That output set distinguishes it from conversion siblings (to_wareki/from_wareki) and from enumeration siblings (list_holidays) without needing to name them.

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 / when-not-to-use guidance and no routing to alternatives such as count_business_days or list_holidays. Usage is only inferable from the resource itself (you have a date and want it classified), which is implied rather than stated.

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.