Skip to main content
Glama

jimu (renamed to Tax Compass)

和暦と西暦の変換(令和・平成・昭和)

jp_era_convert
Read-onlyIdempotent

Convert between Gregorian dates and Japanese era dates (和暦: 昭和 Showa, 平成 Heisei, 令和 Reiwa), handling the exact switch days (昭和 began 1926-12-25, 平成 began 1989-01-08, 令和 began 2019-05-01) and 元年 (first year). Use it when filling Japanese forms, contracts or documents that require 和暦, or when reading a 和暦 date. Modes: {to:"wareki", date:"YYYY-MM-DD"}; {to:"seireki", era, year, month, day}; {to:"wareki", year_only} (lists every era in that year). A 平成 date after 2019-04-30 (e.g. 平成31年5月1日) is read as that day and the correct 令和 form is returned with a note; a Showa date from 1989-01-08 on (e.g. 昭和64年1月8日, Showa 64-01-08), dates that do not exist, and dates before 1926-12-25 return an error.

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": {
      "to": "<to>"
    },
    "name": "jp_era_convert"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYeswareki=西暦から和暦へ、seireki=和暦から西暦へ
dayNo
eraNoto が seireki の時の元号
dateNoto が wareki の時の西暦の日(YYYY-MM-DD)
yearNo元号の年(元年は 1)
monthNo
year_onlyNoto が wareki で、年だけ変える時の西暦の年

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 readOnly/idempotent/non-destructive/closed-world, so the description's job is to add operational detail — and it does: era boundary dates, 元年 handling, conversion of out-of-range era dates (平成31年5月1日) with a note, and errors for nonexistent or pre-1926-12-25 dates. Only the shape of the returned 'note' is left implicit, which the output schema presumably covers.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded purpose sentence, then a compact 'Modes:' block, then an edge-case sentence. Dense but every clause carries information; the final sentence is long and could be split, but nothing is redundant.

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?

For a 7-parameter, mode-switching converter, the description supplies the mode dispatch, era semantics, boundary behavior and failure cases, while the output schema covers return values and annotations cover the safety profile. Nothing an agent needs to invoke it correctly is missing.

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

Parameters5/5

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

With 71% schema coverage, the description adds real value by spelling out the three parameter combinations ({to:'wareki', date}, {to:'seireki', era, year, month, day}, {to:'wareki', year_only}) that the flat schema cannot express as a discriminator. It also clarifies that 元年 is encoded as year 1, resolving the main ambiguity in the `year` parameter.

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 bidirectional operation (Gregorian ↔ Japanese era dates) and enumerates the supported eras (昭和/平成/令和) with their switch dates, which makes it unmistakably distinct from the tax/holiday/deadline siblings. An agent can select it without opening the schema.

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?

Explicitly names the situations that call for it: filling Japanese forms, contracts or documents requiring 和暦, or reading a 和暦 date. It does not name a when-not condition or a sibling alternative, but the domain is disjoint enough that the positive guidance is sufficient.

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