ThinAir Geo

locate

Read-onlyIdempotent

Snap one coordinate to the road network and return the matched road's context: name, road class, speed limit, bearing, snap distance, side of street, truck legality, and toll/ferry/highway/bridge/tunnel flags — plus the IANA timezone. Use to answer 'what road is this point on and what are its rules?' for fleet/telematics snapping, geofence edge checks, or enriching a GPS fix. Set include_elevation for terrain-sourced point elevation_m; grade_pct is a forward-compatible field that stays null for now. Returns matched:false when no routable road is near the point — never a guess.

Input Schema

TableJSON Schema

Name	Required	Description
`lat`	Yes	Latitude
`lon`	Yes	Longitude
`units`	No	Unit system for the human summary — auto-detected (US/UK → imperial) when omitted.
`costing`	No	Travel profile scoping edge access/legality. Default 'auto'.
`include_elevation`	No	Opt-in to point elevation — populates elevation_m/elevation_ft from terrain data (null with an 'elevation_unavailable' warning only where terrain isn't covered). grade_pct is a forward-compatible field that stays null for now (reserved for an elevation-enhanced road network).

Output Schema

TableJSON Schema

Name	Required	Description
`meta`	No
`road`	No
`items`	No
`geojson`	No
`matched`	No
`metrics`	No
`summary`	No
`location`	No
`timezone`	No	IANA timezone for the point, or null unless timezone_status is resolved. Contains information from timezone-boundary-builder, which is made available under the Open Database License (ODbL) v1.0. Timezone boundaries © OpenStreetMap contributors. US legal-zone cross-check: U.S. Department of Transportation, Bureau of Transportation Statistics (public domain).
`warnings`	No
`grade_pct`	No
`elevation_m`	No
`display_hint`	No
`elevation_ft`	No
`timezone_status`	No
`timezone_artifact_version`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 10, 2026

addedOutput schema / properties / timezone / description

Added value: +"IANA timezone for the point, or null unless timezone_status is resolved. Contains information from timezone-boundary-builder, which is made available under the Open Database License (ODbL) v1.0. Timezone boundaries © OpenStreetMap contributors. US legal-zone cross-check: U.S. Department of Transportation, Bureau of Transportation Statistics (public domain)."

addedOutput schema / properties / timezone_artifact_version

Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / timezone_status

Added value: +{
+  "enum": [
+    "resolved",
+    "boundary_ambiguous",
+    "source_conflict",
+    "not_covered",
+    "unavailable"
+  ],
+  "type": "string"
+}

AddedAug 17, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Beyond the readOnly/openWorld/idempotent annotations, it discloses a no-guess failure mode ('Returns matched:false ... never a guess'), the forward-compatible null behavior for grade_pct, and the elevation-unavailable warning. This is rich non-obvious behavior.

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?

Four sentences with no filler; the key purpose and output list are front-loaded, followed by usage guidance and failure behavior. The dense but organized structure lets an agent parse the essentials quickly.

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

Completeness5/5

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

With an output schema present plus full parameter coverage, the description still adds complete operational context: failure return, optional elevation behavior, and output field caveat. No critical calling context is missing.

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 the baseline applies; lat/lon/units/costing are already documented in the schema. The description only restates include_elevation behavior rather than adding new parameter-level semantics beyond the schema.

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

Purpose5/5

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

The description opens with a specific verb and resource ('Snap one coordinate to the road network') and enumerates the returned road context (name, road class, speed limit, bearing, etc.). It frames the tool's question ('what road is this point on and what are its rules?'), which clearly separates it from geocoding or direction siblings.

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

Usage Guidelines4/5

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

It states explicit use contexts: fleet/telematics snapping, geofence edge checks, and enriching a GPS fix. It does not name sibling tools explicitly or provide when-not-to-use exclusion, but the use cases are clear enough to guide selection.

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

All ThinAir Geo tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?