Skip to main content
Glama
Sign In
Adeniyikayodee

ng-postcode

by Adeniyikayodee
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Find the postcode at a location

find_postcode_at_location
Read-onlyIdempotent

Get the postcode of the nearest building to a latitude/longitude coordinate in Nigeria; optionally set a search radius in metres.

Instructions

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.

Input Schema

NameRequiredDescriptionDefault
latitudeYesLatitude in decimal degrees, e.g. 7.6211.
longitudeYesLongitude in decimal degrees, e.g. 5.2214.
max_distance_mNoSearch radius in metres. Defaults to 25.

Output Schema

NameRequiredDescriptionDefault
areaYesEnclosing area code, e.g. EK-01-A03-FK.
noteNoWhy the answer may be incomplete, such as a test key.
unitYes
depthNoHow deep the match goes, e.g. unit.
foundYesFalse when no building is within the radius.
stateYes
messageYes
districtYes
radius_mYesThe radius the API actually applied.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.4.5
    • addedOutput schema / properties / note
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Why the answer may be incomplete, such as a test key.",
+  "title": "Note"
+}
  2. Changed2 schema fields changedv0.4.1
    • addedInput schema / properties / latitude / description
      Added value: +"Latitude in decimal degrees, e.g. 7.6211."
    • addedInput schema / properties / longitude / description
      Added value: +"Longitude in decimal degrees, e.g. 5.2214."
  3. First observedv0.2.4

TDQS

A3.8/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description adds genuinely new behavioral context beyond the annotations: output is config-dependent, with names and house addresses withheld unless NG_POSTCODE_MAX_LEVEL >= 2, which tells the agent to expect redacted results in the default configuration.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, zero waste, with the core action and geographic scope front-loaded and the conditional output-redaction caveat following. Every sentence carries information the agent needs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need no explanation, and the description covers the geographic scope plus the redaction behavior. It stops short of noting what happens when no building falls within max_distance_m, which would be useful for a proximity search, but overall it is sufficient to call the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so latitude, longitude, and max_distance_m (with its 25 m default and 250 m cap) are already fully documented in the schema. The description adds no syntax or format detail beyond that, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Return the postcode of the nearest building to a coordinate') and constrains it geographically to Nigeria. It does not name or contrast with any sibling (lookup_postcode, resolve_address, etc.), so the agent must infer the distinction from the coordinate-based framing, but the purpose itself is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the input shape: it is the tool for converting a lat/long to a postcode. There is no explicit when-to-use versus alternatives such as lookup_postcode or resolve_address, and no stated exclusions (e.g., what to do for coordinates outside Nigeria).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools