ThinAir Geo

batch_geocode

Read-onlyIdempotent

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.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`addresses`	Yes	Array of addresses to geocode (max 50 per batch)

Output Schema

TableJSON Schema

Name	Required	Description
`items`	No
`geojson`	No
`metrics`	No
`summary`	No	Map of scalar facts the LLM should surface verbatim
`display_hint`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed11 schema fields changedAug 17, 2026

changedInput schema / properties / addresses / description

Previous value: -"Array of addresses to geocode"New value: +"Array of addresses to geocode (max 50 per batch)"

addedInput schema / properties / addresses / items / maxLength
```
Added value: +2000
```
addedInput schema / properties / addresses / maxItems
```
Added value: +50
```
changedOutput schema / additionalProperties
```
Previous value: -falseNew value: +true
```

addedOutput schema / properties / items / items / properties / cross_street_kind

Added value: +{
+  "enum": [
+    "street",
+    "route"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / items / items / properties / cross_street_route

Added value: +{
+  "maxLength": 128,
+  "minLength": 1,
+  "type": "string"
+}

addedOutput schema / properties / items / items / properties / intersection_precision

Added value: +{
+  "enum": [
+    "geometric_crossing",
+    "tangent_intersection",
+    "centroid_cluster",
+    "approximate"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / items / items / properties / intersection_type

Added value: +{
+  "enum": [
+    "corner",
+    "interchange"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / items / items / properties / street_kind

Added value: +{
+  "enum": [
+    "street",
+    "route"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / items / items / properties / street_route

Added value: +{
+  "maxLength": 128,
+  "minLength": 1,
+  "type": "string"
+}

addedOutput schema / properties / metrics
```
Added value: +{}
```

Changed1 schema field changedMay 5, 2026

addedOutput schema / properties / geojson

Added value: +{
+  "additionalProperties": true,
+  "properties": {
+    "features": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "geometry": {
+            "anyOf": [
+              {
+                "additionalProperties": true,
+                "properties": {
+                  "coordinates": {},
+                  "geometries": {
+                    "items": {},
+                    "type": "array"
+                  },
+                  "type": {
+                    "anyOf": [
+                      {
+                        "enum": [
+                          "Point",
+                          "LineString",
+                          "Polygon",
+                          "MultiPoint",
+                          "MultiLineString",
+                          "MultiPolygon",
+                          "GeometryCollection"
+                        ],
+                        "type": "string"
+                      },
+                      {
+                        "type": "string"
+                      }
+                    ]
+                  }
+                },
+                "required": [
+                  "type"
+                ],
+                "type": "object"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "id": {
+            "type": [
+              "string",
+              "number"
+            ]
+          },
+          "properties": {
+            "additionalProperties": {},
+            "type": "object"
+          },
+          "type": {
+            "const": "Feature",
+            "type": "string"
+          }
+        },
+        "required": [
+          "type",
+          "geometry"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "type": {
+      "const": "FeatureCollection",
+      "type": "string"
+    }
+  },
+  "required": [
+    "type",
+    "features"
+  ],
+  "type": "object"
+}

Changed1 schema field changedMay 1, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "display_hint": {
+      "additionalProperties": true,
+      "properties": {
+        "layout": {
+          "anyOf": [
+            {
+              "enum": [
+                "summary",
+                "table",
+                "summary+table",
+                "map",
+                "chart+table"
+              ],
+              "type": "string"
+            },
+            {
+              "type": "string"
+            }
+          ]
+        },
+        "map_layers": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "preferred_charts": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "sections": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        }
+      },
+      "required": [
+        "layout"
+      ],
+      "type": "object"
+    },
+    "items": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "confidence": {
+            "type": "number"
+          },
+          "error": {
+            "type": "string"
+          },
+          "input": {
+            "type": "string"
+          },
+          "label": {
+            "type": "string"
+          },
+          "lat": {
+            "type": "number"
+          },
+          "layer": {
+            "type": "string"
+          },
+          "lon": {
+            "type": "number"
+          },
+          "source": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "summary": {
+      "additionalProperties": {},
+      "description": "Map of scalar facts the LLM should surface verbatim",
+      "type": "object"
+    }
+  },
+  "type": "object"
+}

Changed1 schema field changedApr 29, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
First observedApr 28, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already provide readOnlyHint, openWorldHint, and idempotentHint, reducing the burden on the description. The description adds useful behavioral context by noting 'structured per-record results,' which indicates the response format for individual addresses, and reiterates the 'Max 50 per batch' limit. It doesn't specify error handling for partial failures, but with annotations covering safety, this is adequate.

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?

The description is two concise sentences: the first states the core purpose, the second gives usage guidance and the batch limit. No wasted words, making it efficiently front-loaded and easy to parse.

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?

For a simple batch tool with one parameter, an output schema, and strong annotations, the description is complete. It covers the key operational constraints (bulk usage, max batch size, per-record results) without needing to elaborate on return values, which are presumably documented in the output schema.

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%: the single 'addresses' parameter is fully described as 'Array of addresses to geocode (max 50 per batch).' The tool description repeats this limit and doesn't add any additional semantic detail beyond what the schema already provides, so it meets the baseline for high schema coverage.

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 clearly states the tool's function: 'Geocode multiple addresses in one request with structured per-record results.' It uses a specific verb ('geocode') and resource ('multiple addresses'), and distinguishes itself from the sibling 'geocode' tool by emphasizing batch processing.

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

Usage Guidelines5/5

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

The description explicitly directs use: 'Use for bulk operations instead of repeated single geocode calls.' This provides both a when-to-use (bulk) and a when-not-to-use (as a substitute for repeated single calls), clearly differentiating it from the alternative geocode tool.

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?