jp-address-mcp
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| normalize_jp_addressA | Normalize and verify a Japanese postal address. Splits a raw Japanese address string into structured fields (prefecture, city, town, block number, building, room) and returns a verification flag plus lat/lng. Handles messy input: full-width chars, mixed hyphens, romaji, and building/room separation that generic parsers miss. Use whenever you need to register, validate, or route a Japanese address reliably. |
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 1 tool
Only one tool exists, so there is no possibility of confusion. The tool's purpose is unambiguous and clearly described.
The single tool name follows a clear verb_noun pattern (normalize_jp_address), which is predictable and consistent with common conventions.
With only one tool, the server feels minimal for a dedicated address utility. It earns its place, but the scope is thin and borderline.
The tool consolidates parsing, verification, and geocoding into one operation, covering the full address normalization workflow. There are no obvious gaps for the stated purpose.