ThinAir Geo

weather

Read-only

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.

Input Schema

TableJSON Schema

Name	Required	Description
`lat`	No	Latitude
`lon`	No	Longitude
`units`	No	Temperature/wind units (default: imperial)
`location`	No	Place name or address (will be geocoded)
`forecast_days`	No	Forecast days 1-16 (default 5)
`include_alerts`	No	Include severe weather alerts and warnings (default: true)
`include_forecast`	No	Include multi-day hourly forecast
`include_minutely`	No	Include minute-by-minute precipitation for next 60 min

Output Schema

TableJSON Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 16, 2026
- addedOutput schema / properties / alerts_error
```
Added value: +{
+  "type": "string"
+}
```

Changed10 schema fields changedAug 17, 2026

addedInput schema / properties / forecast_days / maximum
```
Added value: +16
```
addedInput schema / properties / forecast_days / minimum
```
Added value: +1
```
addedInput schema / properties / lat / maximum
```
Added value: +90
```
addedInput schema / properties / lat / minimum
```
Added value: +-90
```
addedInput schema / properties / location / maxLength
```
Added value: +2000
```
addedInput schema / properties / lon / maximum
```
Added value: +180
```
addedInput schema / properties / lon / minimum
```
Added value: +-180
```
changedOutput schema / additionalProperties
```
Previous value: -falseNew value: +true
```

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"
+}

addedOutput schema / properties / items

Added value: +{
+  "items": {
+    "additionalProperties": {},
+    "type": "object"
+  },
+  "type": "array"
+}

Changed1 schema field changedMay 1, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "alerts": {
+      "anyOf": [
+        {
+          "items": {
+            "additionalProperties": {},
+            "type": "object"
+          },
+          "type": "array"
+        },
+        {
+          "additionalProperties": {},
+          "type": "object"
+        }
+      ]
+    },
+    "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"
+    },
+    "metrics": {
+      "items": {
+        "additionalProperties": {},
+        "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.2/5.0

Behavior4/5

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

Annotations declare readOnlyHint=true and openWorldHint=true, so the safety profile is already known. The description adds useful behavioral detail beyond annotations by specifying that the response includes current conditions, forecasts, severe alerts, and minutely precipitation. It does not contradict annotations and gives the agent a clear sense of the tool's data scope.

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 sentences with no filler. The first sentence states the core function and key included data; the second provides concrete use cases. Every clause earns its place.

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

Completeness4/5

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

The description is complete enough given the annotations, 100% schema coverage, and the presence of an output schema. It names the core data products and use cases. It does not explicitly discuss rate limits, fallback behavior when no location is supplied, or exact return structure, but these are either covered by annotations/schema or are not required for calling the tool.

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 every parameter already has a meaningful description. The tool description adds general context about location and weather features but does not explain parameter nuances such as how to choose between lat/lon and the geocoded 'location' parameter, which is acceptable because the schema already covers these.

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 states a specific action ('Get current and forecast weather') on a clear resource ('a location') and explicitly names notable outputs ('severe weather alerts', 'minute-by-minute precipitation'). This makes the tool's function immediately identifiable and distinct from the broader sibling list.

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?

The description gives clear use cases: 'destination conditions, travel planning, or route risk assessment.' It does not mention explicitly when not to use the tool or name alternative siblings, but the use-case framing is sufficient for an agent to select it appropriately in most contexts.

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?