Skip to main content
Glama

Torify — Japan Locale APIs for AI Agents

Japanese Era Date Converter [Torify namespace — official]

torify_wareki.convert
Read-onlyIdempotent

Convert between Japanese era dates (wareki) and Gregorian. Supports Meiji/Taisho/Showa/Heisei/Reiwa. Handles era boundary dates accurately. 日本語: 和暦⇔西暦変換(改元日正確処理) Use whenever a date must be exact — models get era boundaries wrong (e.g. Showa 64 = Jan 1-7 1989 only). Do not compute wareki from memory. [Torify namespace — official]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dayNoDay 1-31 / 日(1〜31)
eraNoEra name (Reiwa/Heisei/Showa/Taisho/Meiji or 令和/平成/昭和/大正/明治)
dateNoGregorian date YYYY-MM-DD, required when direction=g2w / 西暦日付(direction=g2w 時必須)
monthNoMonth 1-12 / 月(1〜12)
eraYearNoEra year (1 or greater) / 元号年(1以上)
directionYesg2w: Gregorian to wareki / 西暦→和暦, w2g: wareki to Gregorian / 和暦→西暦

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dayNo日(w2g 時)
eraNo元号(例: 令和)
yearNo西暦年(w2g 時)
monthNo月(w2g 時)
eraYearNo元号年
eraRomajiNo元号ローマ字(例: Reiwa)
formattedNoフォーマット済み日付文字列
eraYearLabelNo元号年ラベル(例: 元年)

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already provide readOnlyHint and idempotentHint, covering the safety profile. The description adds that it handles boundary dates accurately with an example, which is useful but not extensive. No contradictions with annotations.

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 sentences with a clear action, supported eras, a notable feature, and a bold warning. No filler; every sentence earns its place.

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?

Given the output schema exists, the description adequately covers the tool's purpose, supported eras, accuracy feature, and usage advice. No gaps for this level of complexity.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents all parameters well. The description adds context about supported eras and boundary handling but does not enrich parameter meanings beyond 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 'Convert between Japanese era dates (wareki) and Gregorian' and lists supported eras, so the verb and resource are specific. However, it does not differentiate from its sibling 'wareki.convert', missing an opportunity to clarify when to choose this over the sibling.

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?

It explicitly says 'Use whenever a date must be exact' and warns against computing from memory, providing clear context. However, it does not mention when not to use or suggest alternatives like the sibling tool.

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.

TDQS

A3.7/5.0
Disambiguation1/5

The tool set contains exact duplicates for 10 tools (e.g., company.fullProfile and torify_company.fullProfile). An agent cannot distinguish between them, leading to confusion and potential misselection. The purpose of having both namespaced and non-namespaced versions is unclear.

Naming Consistency2/5

Naming is inconsistent: some tools use a dot-separated namespace (e.g., company.fullProfile), while others have a prefix (torify_company.fullProfile). Some tools lack the prefix (e.g., geo.geocode) while their duplicates have it (torify_geo.geocode). No consistent verb_noun pattern; naming conventions are mixed.

Tool Count2/5

With 24 tools, the count is high, and half are duplicates. The effective unique tool count is 12, which is reasonable for the domain, but the duplication inflates the count unnecessarily, making the surface seem bloated and confusing.

Completeness4/5

The tool set covers key Japanese locale operations: corporate lookup, invoice validation/verification, geocoding, postal lookup, name romanization, kanji conversion, law search, and wareki conversion. However, there are no tools for updating or deleting data, which is expected since these are read-only or verification APIs. Minor gaps like missing station/landmark geocoding are noted but acceptable.