Skip to main content
Glama

Server Details

Location & routing intelligence for AI agents — geocoding, truck routing, traffic, weather, and place search.

Ownership verified
Status
Healthy
Uptime
100.0% over the last 24 hours
OAuth
Works in Glama
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
ChatGPT
–
Claude
ThinAir Geo

TDQS

A4.1/5.0

Scored across 19 tools

Disambiguation5/5

The descriptions actively partition the space with explicit cross-references: geocode vs geocode_structured vs batch_geocode vs resolve_intersection are separated by input shape, explore vs search_places by region-vs-category intent, locate vs reverse_geocode vs map_match vs trace_attributes by road-context vs address vs route-line vs per-segment attributes. Nearly every tool names its nearest neighbor and states when not to use it. The only mildly adjacent pair (map_match / trace_attributes) is clarified in both descriptions.

Naming Consistency3/5

All names are snake_case and readable, but the grammatical convention is mixed: verb_noun (batch_geocode, search_places, issue_api_key), noun_verb (place_get, geofence_contains), and bare nouns or adjectives (directions, traffic, weather, quota, isochrone, explore, locate). An agent can still infer purpose, but there is no single predictable pattern to guess a name from.

Tool Count4/5

19 tools sits near the upper band, but the domain is genuinely broad — geocoding, routing, matrix, isochrones, POI/region discovery, geofencing, map matching, traffic, weather, and account/quota — and each tool maps to a distinct operation rather than a redundant variant. Borderline heavy, but nothing feels padded.

Completeness4/5

The surface is unusually thorough: forward/reverse/structured/batch geocoding, intersection resolution, stable place lookup, routing with vehicle profiles, distance matrices, isochrones, geofence containment, GPS map matching plus trace attributes, traffic, weather, and quota/API-key handling. Minor gaps remain — no route optimization / multi-stop sequencing and no elevation or static-map endpoint — but they are workaround-able rather than blocking.

Publisher details

Operator
ThinAir Telematics, LLC · Publisher source
Operator website
https://geo.thinair.co
Vendor relationship
First-party · Publisher source
Privacy policy
Not provided
Trust center
Not available
Restrictions
Free tier available without a credit card. Paid plans add higher quotas and dedicated API keys. Authentication via OAuth 2.1 (keyless, no custom OAuth app required) or Bearer API key. No admin approval or allowlisting required. Global coverage, no regional restrictions. · Publisher source

Available Tools

19 tools
batch_geocodeA
Read-onlyIdempotent
Inspect

Geocode multiple addresses in one request with structured per-record results. Use for bulk operations instead of repeated single geocode calls. Max 50 per batch.

Inputs: addresses (required). Returns: items, geojson, metrics, summary, +1 more

directionsA
Read-onlyIdempotent
Inspect

Generate routes, ETAs, and turn-by-turn directions between locations. Live traffic is post-route ETA enrichment; this enrichment does not change the returned path (path_influenced=false), which does not prove whether the routing engine used admitted current speeds to choose it. Truck traffic adjustments are slowdown-only. Supports car / truck / motorcycle / pedestrian / bicycle, with hazmat + dimension + toll avoidance for commercial routing. ETAs are returned as ISO 8601 with timezone offset (in the destination's local timezone). Use vehicle_profile presets (10 total — DRY_VAN_53, FLATBED_48/_40, STEP_DECK, TANKER, BOX_TRUCK_26, AUTO_CARRIER, SPRINTER_VAN, DOUBLE_TRAILER, OVERSIZE) when routing trucks — they set height/weight/length in one parameter.

Inputs: to (required), from (required), via, units, +18 more. Returns: items, geojson, metrics, summary, +25 more

distance_matrixA
Read-onlyIdempotent
Inspect

Compute road distances and travel times for every origin → destination pair. Endpoints accept free-text addresses or 'lat,lon' strings; N × M is capped at 625 pairs. Use for fleet dispatch, nearest-depot, and bulk ETA tables. Durations do NOT include live or historical traffic — see duration_basis; use directions for a traffic-adjusted ETA between two specific points.

Inputs: origins (required), destinations (required), units, costing. Returns: meta, units, matrix, costing, +5 more

exploreA
Read-onlyIdempotent
Inspect

BROWSING / DISCOVERY search — administrative places (cities, neighbourhoods, boroughs, counties, regions) near a location. Use this when the user is exploring a REGION rather than looking for a specific category. Supports population filtering ('cities > 100k'), ranking by significance or distance, and layer filtering (locality / neighbourhood / borough / county / region). Venues, addresses and streets are NOT served here — for venues and POI categories (gas, food, charging, etc.) use search_places instead. Each result carries its distance in the caller's units and a bearing from the center.

Inputs: lat, lon, size, sort, +6 more. Returns: meta, items, geojson, metrics, +2 more

geocodeA
Read-onlyIdempotent
Inspect

Convert an address, place name, street, or intersection into coordinates and structured location results. Use when input is text and you need coordinates before routing, weather, or search. Supports street-level resolution and proximity biasing.

Inputs: query (required), size, layers, focus_lat, +2 more. Returns: items, geojson, metrics, summary, +2 more

geocode_structuredA
Read-onlyIdempotent
Inspect

Geocode from discrete address components (address, locality, region, postalcode, country) instead of one free-text string. Use when the input is already fielded (forms, CRM records, stop tables) — skips free-text parsing so components can't be mis-tokenized. At least one component is required. No cross-street field: for named intersections use resolve_intersection or geocode.

Inputs: size, region, address, country, +5 more. Returns: items, geojson, metrics, summary, +2 more

geofence_containsA
Read-onlyIdempotent
Inspect

Tests one or more points for containment inside a polygon you supply as GeoJSON (Polygon, MultiPolygon, or a Feature/FeatureCollection wrapping one). Pure geometry against your own shape - it does not search a place index, so use explore or search_places to find what's near a point instead. Boundary points count as contained. Up to 1000 points per call, against a polygon of up to 100 rings/parts and 1000 positions per ring; larger inputs are rejected. A polygon with more than about 1,500 positions in total must be sent as a GeoJSON string (the same GeoJSON, JSON-encoded) instead of as an object. Runs locally with no external lookup, but still counts as one metered request like other tools, so batch points into a single call rather than looping. Errors, rather than returning false, when the polygon is structurally invalid. Returns one boolean per point, in order, plus contained_count and point_count.

Inputs: points (required), polygon. Returns: results, warnings, point_count, contained_count

isochroneA
Read-onlyIdempotent
Inspect

Computes reachability polygons: the area reachable from an origin within given travel-time or travel-distance bands. Use for service coverage, dispatch range, territory design, and 'how far can I get in X minutes' questions; use directions or distance_matrix for a route or distance between specific points instead. Pass multiple bands in one call (contours_minutes:[10,20,30]) for nested polygons in one response, up to 4 bands, defaulting to 15/30/60-minute driving bands if none given. location accepts an address string or 'lat,lon'. costing selects the travel profile (auto default, or truck/bicycle/pedestrian/motorcycle). Read-only and cached. Returns a GeoJSON FeatureCollection of nested polygon contours, one per band.

Inputs: location (required), costing, contours_km, truck_height, +2 more. Returns: items, geojson, metrics, summary, +1 more

issue_api_keyA
Read-onlyIdempotent
Inspect

Get the link to create a ThinAir GEO (geocoding/routing) API key. Returns console_url (the signed-in ThinAir Geo console) and instructions; it does NOT return a key and does not create, rotate or revoke any key. The owner signs in, creates the key there and sees it once in their own browser, then sends it as an Authorization: Bearer header. Existing keys keep working. Counts as 1 query against your daily quota. NOTE: keys created there work ONLY against ThinAir Geo — they do NOT authenticate against ThinAir Data, which issues its own ta_data_* keys from its own identically-named tool.

Inputs: no named parameters. Returns: note, plan, error, status, +2 more

locateA
Read-onlyIdempotent
Inspect

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. Read road_status, not matched alone: matched — a road was found and road is filled; no_road_nearby — a real answer: no routable road is near the point for this travel profile; unavailable — the road lookup could not be answered right now, so matched:false / road:null say nothing about the point, retryable is true, and the timezone and any requested elevation are still looked up separately (see timezone_status and warnings). Never a guess.

Inputs: lat (required), lon (required), units, costing, +1 more. Returns: meta, road, items, geojson, +14 more

map_matchA
Read-onlyIdempotent
Inspect

Map matching snaps raw GPS breadcrumbs to the road network. Feed a recorded trace (2–100 points) and get back the road-accurate route that was actually driven: matched geometry, distance, time, road names, and a 0–1 match confidence. matched: true only means a route was returned — gate on match_status: full when every input point was matched or interpolated onto the road network and the match is one continuous section, none when no point was, otherwise partial. coverage gives the per-point counts, unmatched_ranges (0-based input indexes that did not match) and route_sections (above 1, the geometry, distance and time cover only the first section — split the trace there). match_status is null, with coverage.unavailable_reason, when the per-point check could not be completed. Sparsely-reported traces (consecutive fixes farther apart than the default breakage distance — e.g. fleet units reporting every several minutes on a highway) can split into multiple sections; increase breakage_distance_m to keep them as one. Total matched distance is limited to 200 km per call — split longer sparse traces by distance, not only by the 100-point cap. Use for fleet trace cleanup, mileage from GPS logs, and reconstructing routes from telemetry. road_names come from the route's maneuver points, so they cover the roads the route turns onto or starts on — for the name of every segment actually travelled, use trace_attributes. For planning a route between places, use directions instead.

Inputs: shape (required), costing, search_radius, vehicle_profile, +1 more. Returns: legs, meta, costing, geojson, +10 more

place_getA
Read-onlyIdempotent
Inspect

Look up a place by its stable ThinAir id (ta_place_… / ta_intersection_…) as returned in the id field of geocode, reverse_geocode, search_places, or resolve_intersection results. Ids are deterministic and survive re-serves — safe to store as favorites or foreign keys. Returns the canonical name, label, layer, and coordinates. Unknown or expired ids error with re-search guidance.

Inputs: id (required). Returns: id, lat, lon, meta, +5 more

quotaA
Read-only
Inspect

Check current usage, remaining limits, plan, and quota breakdown for the caller. FREE TO CALL — never counts against your quota, never blocked by it. Use this proactively when the user asks about usage or seems near limits.

Inputs: no named parameters. Returns: mcp, upstream

resolve_intersectionA
Read-onlyIdempotent
Inspect

Resolve a NAMED cross-street (street1 × street2 within a locality/region/country) to a single best coordinate with a confidence score and a fleet-safe fallback. High-confidence tier matches US-metro highway corners; named non-highway streets resolve via the geocoder fallback. For free-form streets use geocode.

Inputs: street1 (required), street2 (required), region, country, +1 more. Returns: meta, admin, feature, warnings, +4 more

reverse_geocodeA
Read-onlyIdempotent
Inspect

Converts a coordinate pair into the nearest addresses, streets, venues, or administrative places, ordered by proximity. Use when starting from GPS or a map position; for text-to-coordinates use geocode, and for a point's road-network context (name, class, speed limit, legality) use locate instead. Read-only and cached. Near the poles (|lat| >= 85 degrees) the index is too sparse for a real nearest match, so this returns no results rather than a distant wrong guess. Returns up to size candidates (default 5, max 40); layers restricts the type returned (address, street, venue, neighbourhood, locality, county, region, country, postalcode, and more). Each result carries a confidence score, layer, label, and coordinates, same shape as geocode.

Inputs: lat (required), lon (required), size, layers. Returns: items, geojson, metrics, summary, +2 more

search_placesA
Read-onlyIdempotent
Inspect

CATEGORY-specific POI search near a point — gas stations, truck stops, restaurants, charging stations, etc. Use this when the user has a specific TYPE of place in mind (food / health / retail / fuel / accommodation / nightlife / transport / government / recreation). For broader DISCOVERY (e.g. 'cities within 50 miles' or 'venues by population'), use explore instead.

Inputs: lat, lon, limit, query, +6 more. Returns: meta, items, geojson, metrics, +2 more

trace_attributesA
Read-onlyIdempotent
Inspect

Trace attributes return road/network attributes for matched traces. Feed a GPS breadcrumb trail (2–100 points) and get per-segment road names, road classes, speed limits, surfaces, truck-route flags, and segment lengths along the matched route, plus a matcher confidence score. Sparsely-reported traces (consecutive fixes farther apart than the default breakage distance — e.g. fleet units reporting every several minutes on a highway) can split into multiple sections; increase breakage_distance_m to keep them as one. Total matched distance is limited to 200 km per call — split longer sparse traces by distance, not only by the 100-point cap. Use to audit what roads a vehicle actually used (speed-limit compliance, truck-route adherence, surface checks). For just the matched route line, use map_match.

Inputs: shape (required), costing, search_radius, vehicle_profile, +1 more. Returns: meta, edges, admins, costing, +10 more

trafficA
Read-only
Inspect

Retrieve live traffic conditions, congestion, and speed for a location. Use when traffic is needed independently of routing — for corridor monitoring, area congestion, or incident checks. COVERAGE: live data for ~30 major US metros; returns degraded or empty values outside these areas. For rural coordinates, qualify the response (e.g. 'no live traffic coverage here — showing free-flow speeds').

Inputs: lat (required), lon (required), units. Returns: items, geojson, metrics, summary, +1 more

weatherA
Read-only
Inspect

Get current and forecast weather for a location, including severe weather alerts and minute-by-minute precipitation. Use for destination conditions, travel planning, or route risk assessment.

Inputs: lat, lon, units, location, +4 more. Returns: items, alerts, geojson, metrics, +3 more

Tool Schema Changelog

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

Loading tool schema changelog…

    Related MCP Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Remote MCP server that lets AI assistants read tracked competitive intelligence — competitor news, reviews, website changes, social posts and ads — and act on it by managing projects, competitors, battle cards, reports and canvases. Every answer carries a source and a date, and write actions only publish when explicitly shared.
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables brand visibility monitoring across major AI platforms like ChatGPT, Claude, Gemini, and Perplexity. It allows users to track visibility scores, analyze competitor data, and receive actionable insights to improve AI-generated brand recommendations.
      16
      11 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Browse IndustryLens's published competitive-intelligence reports and head-to-head competitor comparisons from any AI agent — real, source-backed data.
      MIT
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources