Skip to main content
Glama

Postal codes and places

Find a place: its state, county or district and postal codes

find_place
Read-onlyIdempotent

What is the postal code / ZIP / postcode / PIN code of a town, and which state, province, region, county, district or local government area is it in? Returns matching places (largest first) with admin1 (state/province/region), admin2 (county/district/LGA), population, coordinates, timezone and postal codes, plus postal codes nearby. Covers every place with 1,000+ people worldwide and every place in GeoNames postal files (124 countries). Use the country argument or "Town, Country" / "Town, State" to disambiguate.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>"
    },
    "name": "find_place"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesPlace name in Latin script, e.g. "Geelong", "Springfield, Illinois", "Kolar, India", "München".
adminNoOptional state, province, region, county or district to narrow the match, e.g. "Illinois", "Karnataka", "Bayern".
countryNoOptional. Country as an ISO 3166-1 alpha-2 code (AU, US, GB, DE, IN, PH, ...) or an English country name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-open-world behavior, and the description adds substantive context beyond them: results are ranked largest first, the dataset scope (1,000+ population worldwide, GeoNames postal files for 124 countries), and that nearby postal codes are included. It does not mention result limits or how ambiguous names are truncated, which is the main remaining gap.

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

Conciseness4/5

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

Two dense sentences that lead with the user-facing question and then enumerate outputs, coverage and disambiguation. The postal-code synonym list is slightly padded but defensible for query matching; nothing else is wasted.

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?

With no output schema, the description correctly spells out the returned fields and ranking, which is exactly what the agent needs. Missing only result-count limits and handling of very ambiguous names for a tool with three simple parameters.

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 coverage is 100% and each parameter already carries an example, so the schema does the heavy lifting. The description's note about disambiguating via the country argument or a "Town, State" name string adds only a little meaning beyond the existing examples.

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?

The description states a concrete verb+resource: look up a town's postal codes and the administrative divisions (admin1/admin2) it falls in, and it enumerates the returned fields. It is clearly a forward geocoding lookup, but it never names or contrasts with the sibling lookup_postal_code, so an agent must infer the direction split itself.

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?

"Use the country argument or 'Town, Country' / 'Town, State' to disambiguate" gives real disambiguation guidance, and the coverage statement implies when the tool is applicable. However, there is no explicit when-not or named alternative, so selection against lookup_postal_code is only implied.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources