ng-postcode
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NG_POSTCODE_API_KEY | No | API key for the NIPOST postcode API. Validation works without a 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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| validate_postcodeA | Check a postcode's structure offline and return its canonical forms and segments. Free and instant. Does not confirm the code is assigned to a building; use lookup_postcode for that. |
| lookup_postcodeB | Confirm a postcode is assigned and, at higher levels, return its address details. |
| autocomplete_postcodeB | Suggest completions for the next segment of a partly typed postcode. |
| find_postcode_at_locationA | Return the postcode of the nearest building to a coordinate in Nigeria. Names and the house address are withheld unless NG_POSTCODE_MAX_LEVEL is 2 or more. |
| resolve_addressA | Turn a described Nigerian address into a postcode, only as precisely as the evidence allows. A full building code comes only from a postcode written in the address, a location
pin, or a landmark that is the address itself. Otherwise the result is an area or
district prefix with a |
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 5 tools
Each tool targets a distinct input/output: autocomplete (partial->completions), validate (offline structure), lookup (assignment + address), find_postcode_at_location (coords->postcode), resolve_address (address text->postcode). The only mild overlap is validate vs lookup, but descriptions explicitly contrast them (offline structural check vs assignment confirmation).
All names are snake_case with a verb_noun feel (autocomplete_postcode, lookup_postcode, validate_postcode, resolve_address). find_postcode_at_location is longer and inserts a preposition, a minor deviation, but still readable and consistent in style.
Five tools is well-scoped for a postcode service, covering forward lookup, reverse lookup, validation, autocomplete, and address resolution with no redundancy or filler.
The surface covers the main lifecycle: autocomplete, validate, lookup, coordinate->postcode, and address->postcode. Minor gaps exist (e.g. no batch lookup or postcode->coordinate reverse), but core workflows are covered.