mcp-server-zipcode-jp
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_zip_codeC | Search zip code data |
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
With only one tool, there is no risk of ambiguity. The single tool's purpose is clear and distinct by default.
The single tool name 'search_zip_code' follows a consistent verb_noun pattern, which is clear and predictable.
A single tool for a zip code server feels minimal. While search might be sufficient, the scope is thin compared to typical CRUD or lookup services for zip codes.
The tool surface appears incomplete for a comprehensive zip code service. Missing operations like get_by_code, reverse lookup, or list prefectures limit the agent's ability to perform related tasks.