Boundr
Server Details
UK administrative boundary data from OS Boundary Line: name search, point lookup, GeoJSON geometries
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Score is being calculated. Check back soon.
Available Tools
7 toolsfind_boundaries_at_pointInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| lat | Yes | Latitude in decimal degrees. Must be between -90 and 90. Example: 51.5074 (central London). | |
| lng | Yes | Longitude in decimal degrees. Must be between -180 and 180. Example: -0.1278 (central London). | |
| boundary_types | No | Optional list of type codes to restrict results, e.g. ["CTY", "LBO"]. All levels are returned if omitted. |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
get_boundary_bboxInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| code | Yes | ONS census / GSS / LAU code, e.g. "E14001592" for Woking. Case-insensitive. |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
get_boundary_by_codeInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| code | Yes | ONS census / GSS / LAU code, e.g. "E09000012". Case-insensitive — "e09000012" resolves to the same boundary. |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
get_boundary_geojson_by_codeInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| code | Yes | ONS census / GSS / LAU code, e.g. "E09000012" for Hackney. Case-insensitive. |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
get_boundary_geojson_simplifiedInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| code | Yes | ONS census / GSS / LAU code, e.g. "E14001592" for Woking. Case-insensitive. | |
| tolerance | No | Simplification tolerance in degrees (WGS-84). Default 0.0001. Increase to 0.001 for county-scale boundaries. |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
list_boundary_type_codesInspect
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", ...}
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Output Schema
| Name | Required | Description |
|---|---|---|
No output parameters | ||
search_boundaries_by_nameInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Full or partial boundary name. Case-insensitive. Examples: "Hackney", "Greater Manchester", "York", "Kent". | |
| boundary_type | No | Optional type code to narrow results, e.g. "LBO" for London Boroughs or "CTY" for Counties. Must be a code from list_boundary_type_codes(); raises ValueError otherwise. |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!