Edition Intelligence Platform

Overview Schema Source Related Servers Discussions Admin

calendar_check

Read-onlyIdempotent

Search Japanese business calendar for holidays, fiscal periods, gift seasons, administrative deadlines, and seasonal business opportunities.

Instructions

日本のビジネスカレンダー情報を検索します。祝日、決算期、贈答シーズン、行政締切、季節性ビジネスの5カテゴリ。

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": {
      "query": "<query>"
    },
    "name": "calendar_check"
  }
}

Input Schema

Name	Required	Description	Default
`query`	Yes	検索クエリ（例: '開業のベストタイミング', 'GW', '確定申告の締切'）

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.6.0May 10, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already indicate read-only, idempotent, and non-destructive behavior. The description adds valuable context by listing the specific categories searched (holidays, financial periods, gift-giving, deadlines, seasonal business), which is beyond the annotations. No contradictions.

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?

The description is a single, clear sentence that immediately states the tool's purpose and lists the categories. No unnecessary words or information.

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 description explains what is searched but does not specify the output format or what exactly is returned. Given no output schema, the agent might lack information about the result structure. However, the clear categories partially compensate.

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?

With 100% schema description coverage, baseline is 3. The description adds meaning by specifying the five categories, which helps the agent formulate appropriate queries beyond the examples provided 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 clearly states the tool searches Japanese business calendar information across five specific categories. The verb 'search' and resource 'calendar information' are explicit. However, it does not differentiate itself from sibling tool 'calendar_list' which might list calendars instead of searching.

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?

The description provides context for usage by listing the five categories, implying search scenarios. However, it does not explicitly state when to use this tool versus alternatives like 'calendar_list' or other search tools, nor does it provide exclusions or prerequisites.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.