Skip to main content
Glama

Japan Calendar

Japanese era to Gregorian

from_wareki
Read-onlyIdempotent

Convert a Japanese era date to a Gregorian date. Accepts 令和8年11月18日, 令和元年5月1日, 平成三十一年四月三十日, R8.11.18, H31/4/30, Reiwa 8.11.18. Rejects dates that did not exist in that era (e.g. 平成31年5月1日).

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": {
      "text": "<text>"
    },
    "name": "from_wareki"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesJapanese era date text

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/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, so the safety profile is covered. The description adds genuinely non-obvious behavior: invalid-in-era dates are rejected, with a concrete counterexample (平成31年5月1日), which prevents a common agent mistake. It does not describe the shape of the returned Gregorian value, which is the remaining gap.

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?

Three sentences, front-loaded with the purpose, then formats, then rejection behavior. Every sentence adds information an agent needs and none repeats the title or schema.

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 single-parameter pure conversion with no output schema, input coverage and error behavior are well documented. The one omission is the return format (e.g. whether the result is YYYY-MM-DD or a longer string), which the agent cannot infer from structured fields.

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 'text' parameter is only described as 'Japanese era date text', so the description carries real weight here. It enumerates accepted syntaxes across kanji numerals, abbreviated Latin forms, and slash/dot separators, which meaningfully expands what the parameter accepts. It does not cover edge cases like whitespace or mixed scripts.

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?

States a specific verb and resource with unambiguous directionality ('Convert a Japanese era date to a Gregorian date'), which implicitly separates it from the inverse sibling to_wareki without naming it. It stops short of an explicit sibling callout, so it is clear but not maximally differentiated.

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 conversion direction; there is no statement of when to prefer this over to_wareki or check_date. The accepted-input examples do give practical guidance on how to call it, but no exclusions or prerequisites are offered.

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.