kenall-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KENALL_API_KEY | Yes | Your Kenall API key |
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 |
|---|---|
| lookup_postal_codeB | Look up address information from a Japanese postal code |
| search_addressB | Search for postal codes by address |
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 2 tools
The two tools perform inverse but clearly distinct operations: postal code to address versus address to postal code. An agent can unambiguously pick the correct tool based on the direction of the query.
Both names follow a verb_noun pattern (lookup_postal_code, search_address) in consistent snake_case. The verbs differ slightly (lookup vs search), but the convention is otherwise predictable and readable.
Two tools is thin, but the server's purpose (Japanese postal code lookup) is inherently narrow and both directions of the mapping are covered. It is borderline minimal rather than clearly well-scoped.
The core domain—bidirectional postal code/address resolution—is fully covered with no dead ends for the primary use case. Minor extras like batch lookup or input validation are absent but not essential.