Skip to main content
Glama

Server Details

UK administrative boundary data from OS Boundary Line: name search, point lookup, GeoJSON geometries

If you are the author of this connector, you can claim ownership. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
ChatGPT
–
Claude
–

TDQS

A4.7/5.0

Scored across 7 tools

Disambiguation5/5

Each tool targets a distinct operation: point lookup, bounding box, metadata by code, full geometry, simplified geometry, type codes listing, and name search. Even the two geometry tools are clearly differentiated by simplification level.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern in snake_case (e.g., find_boundaries_at_point, get_boundary_bbox, list_boundary_type_codes). The naming is predictable and clear.

Tool Count5/5

Seven tools is well-scoped for a UK boundary lookup service. It covers all core operations without being excessive or insufficient.

Completeness5/5

The toolset provides complete coverage for readonly boundary access: name search, point lookup, metadata retrieval, bounding box, and geometry (full and simplified). No obvious gaps for the intended domain.

Available Tools

7 tools
find_boundaries_at_pointAInspect

Find all UK administrative boundaries that geographically contain a coordinate point.

Use this to answer "what county/borough/ward is this location in?" for a latitude/longitude. Returns lightweight metadata only — no geometry. If you need to display a boundary shape, call get_boundary_geojson_by_code() with the returned code.

Multiple boundaries at different administrative levels typically contain the same point (e.g. a ward, a borough, and a county). Filter by boundary_types to restrict which levels are returned.

Call list_boundary_type_codes() first if you are unsure which type codes to use.

Inputs: lat (required), lng (required), boundary_types. Returns: result

get_boundary_bboxAInspect

Get the bounding box and centroid for a boundary by its ONS census code.

Returns min_lat, max_lat, min_lng, max_lng, centroid_lat, centroid_lng. Pass the bbox values directly to Knotsure's sightings_in_bbox() or geographic_summary(). Much cheaper than get_boundary_geojson_by_code() for spatial queries because no geometry is fetched or serialised.

Inputs: code (required). Returns: result

get_boundary_by_codeAInspect

Look up metadata for a single UK boundary by its ONS census code. No geometry.

Use this when you already have a census code (e.g. from search_boundaries_by_name() or find_boundaries_at_point()) and need structured metadata such as area size or type label. If you also need the boundary shape for display or analysis, call get_boundary_geojson_by_code() instead.

ONS census codes (sometimes called GSS codes or LAU codes) are stable identifiers of the form "E09000012" (Hackney), "E10000016" (Kent), etc. The first letter indicates the country: E = England, W = Wales, S = Scotland, N = Northern Ireland.

Inputs: code (required). Returns: result

get_boundary_geojson_by_codeAInspect

Fetch the full GeoJSON geometry for a UK boundary by its ONS census code.

Returns a GeoJSON Feature object (WGS-84 / EPSG:4326) suitable for rendering on a map or performing geometric analysis. The geometry can be large — county and ceremonial county polygons are especially heavy. Only call this when you specifically need the shape; for metadata only use get_boundary_by_code() instead.

IMPORTANT — Leaflet / web maps: use get_boundary_geojson_simplified() instead. The full geometry is large enough to exhaust your context window before you can finish writing the page. The simplified version is safe to embed directly in HTML and indistinguishable from the full shape at normal map zoom levels.

Use this tool only when you need full-fidelity geometry for server-side analysis (e.g. precise point-in-polygon checks, area calculations, clipping).

Obtain the census code from search_boundaries_by_name() or find_boundaries_at_point() before calling this.

Inputs: code (required). Returns: result

get_boundary_geojson_simplifiedAInspect

Fetch simplified GeoJSON for a boundary by its ONS census code.

Safe to embed directly in generated HTML map files. At the default tolerance (0.0001°) a constituency polygon shrinks from ~4,000 vertices to ~200–400 with no visible difference at normal map zoom levels.

Prefer this over get_boundary_geojson_by_code() when writing Leaflet map pages — the full geometry is large enough to exhaust your context window before you can finish writing the HTML.

Inputs: code (required), tolerance. Returns: result

list_boundary_type_codesAInspect

Returns every valid UK boundary type code mapped to its human-readable label.

Call this before using any tool that accepts a boundary_type or boundary_types argument so you know which codes are legal. Passing an unlisted code to another tool raises a ValueError.

Boundary type codes are stable Ordnance Survey identifiers. Common ones:

  • "CTY" → County

  • "LBO" → London Borough

  • "UTA" → Unitary Authority

  • "MTD" → Metropolitan District

  • "DIS" → District

  • "DIW" → District Ward

  • "CCTY" → Ceremonial County

  • "HCTY" → Historic County

  • "WMC" → Westminster Parliamentary Constituency

  • "GLC" → Greater London Constituency

  • "SWC" → Scotland/Wales Constituency

  • "PAR" → Parish

  • "CED" → County Electoral Division

Returns: Dict mapping code → label for all supported boundary types, e.g. {"CTY": "County", "LBO": "London Borough", ...}

Inputs: no named parameters. Returns: object

search_boundaries_by_nameAInspect

Search for UK administrative boundaries by name (case-insensitive partial match).

Use this to discover boundaries when you have a place name but not a code. Returns lightweight metadata only — no geometry. If you need to display or analyse the boundary shape, call get_boundary_geojson_by_code() with the returned code.

Call list_boundary_type_codes() first if you need to filter by type and are unsure which code to use.

Inputs: name (required), boundary_type. Returns: result

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables searching monthly street-level crime, police outcomes, stop and search records, and neighbourhood policing teams published by data.police.uk across England, Wales and Northern Ireland forces plus British Transport Police. Supports flexible area queries by point, polygon, neighbourhood, or whole force over STDIO or Streamable HTTP.
      141 npm
      1
      Apache 2.0
    • A
      license
      A
      quality
      C
      maintenance
      Enables UK postcode lookups, partial-postcode search, reverse geocoding, distance checks between locations, outcode coverage, place-name search, and Scotland-specific administrative data, returning coordinates and ONS/GSS codes. Bulk lookups sort terminated, unknown, and malformed postcodes into separate buckets, and all operations are read-only.
      7
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Provides forward/reverse geocoding, bounding box extraction, nearby places discovery, batch geocoding, route waypoints, and administrative boundary lookup using OpenStreetMap data.
      10
      Apache 2.0
    • A
      license
      A
      quality
      C
      maintenance
      UK property data API and MCP server: checked figures for England and Wales districts (prices, rents, yields, crime, schools, flood risk, EPC) for agents and developers. Keyed access.
      7
      MIT
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources