Skip to main content
Glama

Japan Calendar

Gregorian to Japanese era

to_wareki
Read-onlyIdempotent

Convert a Gregorian date to a Japanese era date (wareki), e.g. 2019-05-01 -> 令和元年5月1日 (R1.5.1). Supports dates from 1873-01-01.

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": "to_wareki"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesGregorian date, YYYY-MM-DD

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and closed-world behavior, so the description needn't repeat safety traits. It adds genuine context beyond them: a minimum supported date (1873-01-01) and the two output renderings (kanji form and R1.5.1 short form). It stops short of saying whether an out-of-range date errors or is clamped.

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?

Two short sentences, front-loaded with the purpose and immediately followed by a concrete example and the range constraint. Nothing is redundant or padded.

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 one-parameter, annotated, read-only tool, this is nearly complete: purpose, example output format, and supported range are all present. The only missing piece an agent might want is error behavior for pre-1873 or malformed dates, which is minor given the schema pattern.

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% and the single date parameter already documents the YYYY-MM-DD format, so the baseline is 3. The description still adds meaning the schema lacks: the valid historical lower bound and a concrete input/output pair that shows how a given param value is interpreted.

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?

The description states a specific verb and resource ('Convert a Gregorian date to a Japanese era date') and the direction of conversion inherently separates it from the inverse sibling from_wareki. The worked example (2019-05-01 -> 令和元年5月1日 / R1.5.1) removes any ambiguity about output shape.

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?

Usage is only implied by the direction of conversion; the description never says when to prefer this over from_wareki or other date tools, nor does it state what happens for dates outside the supported range. The 1873-01-01 floor is the one boundary hint given.

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.