Skip to main content
Glama

WritersLogic developer agents

geo-axis-check

Coordinate axis-order and unit check from a CRS and its area of use — Checks up to 1000 coordinate pairs (or one bounding box) against the EPSG coordinate system you name, for agents handling GIS or map data: it flags longitude/latitude swaps, degrees supplied where metres are expected (or the reverse), values outside the CRS's area of use, and inverted bounds, with the point index and values. It does not reproject, geocode, validate geometry topology or datum, or j

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": {
      "crs": "<crs>"
    },
    "name": "geo-axis-check"
  }
}

Input Schema

NameRequiredDescriptionDefault
crsYesEPSG code in any common form (EPSG:4326, 4326, urn:ogc:def:crs:EPSG::4326) or CRS84. See versions for the snapshot of known codes; others return unknown unless areaOfUse is supplied.
boundsNo[minFirst, minSecond, maxFirst, maxSecond] in the data's own order; its two corners are checked like points and min must not exceed max.
areaOfUseNo[south, west, north, east] degrees; overrides the snapshot for a geographic CRS or supplies one for an unknown geographic code.
coordinatesNo[first, second] pairs exactly as they appear in the data.
declaredOrderNoWhat the data claims: lon-lat or easting-northing means the first value is the east axis; lat-lon or northing-easting means north first. Default: the CRS's EPSG authority order (CRS84: lon-lat).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

Score is being calculated.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources