jp-zengin-name
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| zengin_name_formatA | Turn a payee or payer name into the form Japanese banks accept in transfers (Zengin): half-width katakana, digits, A-Z and a few symbols; small kana made large (ッ->ツ, ャ->ヤ), ー->-, ・->., legal-entity words replaced by the bank abbreviation with the position rule (株式会社 at the start 'カ)', in the middle '(カ)', at the end '(カ'). Accepts kana (hiragana or katakana, full or half width), Latin letters and digits, and legal-entity words in kanji or spelled out (カブシキガイシャ). It does NOT read other kanji: pass the reading. Returns ok, zengin (half-width), display (full-width), length (voiced kana count 2), entities, changes, errors, warnings (code, message in English and Japanese). 振込名義を全銀の形に整える。 |
| zengin_name_checkB | Validate a half-width Zengin name from a CSV or bank file: only allowed characters, no small kana, no full-width characters, spacing, length. Returns ok, length, errors, warnings, abbreviations found. |
| zengin_name_matchA | Decide whether a payer name on a bank statement (half-width, abbreviated) and a customer name (kana reading) are the same, ignoring entity abbreviations, spaces, punctuation, small/large kana and width. Returns match, name_match, key_a, key_b, entity_a, entity_b, entity_type_differs (e.g. ユ) vs 株式会社), errors. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool targets a distinct action on Zengin names: matching two names, formatting a name into Zengin form, and validating an existing Zengin name. The boundaries between format (produce) and check (validate) are clear from the descriptions, so an agent can select the right tool without ambiguity.
All three tools follow the same predictable pattern: a shared `zengin_name_` prefix plus a distinct action verb (`match`, `format`, `check`). There is no mixing of conventions or vague verbs.
Three tools are well-scoped for a narrow domain focused on Japanese Zengin name handling. Each tool covers a distinct operation and none feels redundant or missing for the stated purpose.
The surface covers the core lifecycle: match payer/customer names, format names to Zengin standards, and validate Zengin names from files. Together these operations form a complete workflow for the domain without obvious gaps.