Skip to content

Changelog

The service version is reported by serverInfo.version (MCP) and info.version (OpenAPI). Dates are Japan time. Before 1.0, a minor version can change field names; those changes are marked Changed.

  • Fixed: REST list parameters (such as extra_holidays) can be repeated (a=1&a=2). Before, only the last value was used and the answer was silently wrong. Repeating any other parameter is now a 400 (invalid_input) instead of silently using the last value, and names such as __proto__ are rejected as unknown, as they are over MCP.
  • Fixed: normalize_address matches a town written with a leading 字 or 大字 (for example 与那国町字与那国); before, it matched only the city. The answer’s notes says that the prefix was left out.
  • Changed: 404 and 405 answers carry type (not_found, method_not_allowed). The OpenAPI Error.type lists rate_limited, not_found and method_not_allowed too.
  • Changed: the Japanese-era REST paths are now /v1/japanese-era/to-era (Gregorian → era) and /v1/japanese-era/from-era (era → Gregorian). The era answer fields are input_era, input_era_year (as given) and actual (the correct era date). 0.8.0 used to-date / from-date.
  • from_japanese_era reads a trailing weekday ((水) or 水曜日) and romaji era names (Reiwa 8.10.7). A mismatching weekday sets weekday_mismatch. Malformed kanji numerals and years above 200 are input errors.
  • list_holidays returns total, returned and truncated (count is kept for now).
  • Operations: a build no longer deploys data older than what is live; the monthly refresh runs on the 3rd and the 10th; freshness limits (postal 60 days, corporate numbers 50 days) are shared by the deploy gate and the live check; downloads from the National Tax Agency have time limits.
  • Added: to_japanese_era and from_japanese_era. Era start dates: 大正 1912-07-30, 昭和 1926-12-25, 平成 1989-01-08, 令和 2019-05-01; supported from 1873-01-01. Dates outside an era are converted and marked outside_era; future dates in the current era carry assumes_current_era.
  • Added: machine-readable flags on every answer (estimated, unverified, truncated, not_found, closed, excluded_from_search, exact_match_only, partial, ambiguous, city_not_found, ambiguous_city).
  • Changed: lists use total / returned / truncated (search_corporation_by_name: count → total); a closed corporation is is_closed (renamed from closed in name search, and added to number lookup); check_business_day returns reason_code (weekend, holiday, bank_closure, extra_holiday); normalize_address always returns address, municipality_code and city_candidates.
  • Errors now say whether the input was wrong (Invalid input) or the server was (Server error); REST adds type.
  • A weekly live check also verifies data freshness.
  • The MCP instructions explain which tool to use for what and how to show the corporate-number attribution. search_postal_code explains what to do when a town returns nothing.
  • Added: search_corporation_by_name (prefix search over the National Tax Agency data).
  • Added: lookup_corporate_number (National Tax Agency full bulk data, PDL1.0 attribution).
  • Added: normalize_address (to town level).
  • Postal lookups also cover Japan Post’s individual codes for large-volume business customers (offices, and the office_name search).
  • Added: lookup_postal_code and search_postal_code. Deployment became automatic.
  • First version: the six calendar tools (list_holidays, check_business_day, add_business_days, count_business_days, adjust_to_business_day, last_business_day_of_month) over MCP and REST.

Operated by Momonga