Nasa Eonet

Events

events

Read-onlyIdempotent

Natural hazard events tracked by NASA EONET (the Earth Observatory Natural Event Tracker): wildfires, severe storms, volcanoes, floods, icebergs, landslides, dust and haze. Filter by open or closed status, lookback days, category id, bounding box, reporting source, and magnitude range. Returns each event id, title, category, date-stamped geometry (point or polygon), and links to the reporting agency, answering where wildfires, storms, or eruptions are active now and where they occurred recently.

Input Schema

TableJSON Schema

Name	Required	Description
`bbox`	No	Bounding box: "min_lon,max_lat,max_lon,min_lat" (note non-standard order)
`days`	No	Lookback window in days (default 30, default 30 for closed)
`limit`	No	Max results
`source`	No	Comma-sep source ids (see list_sources)
`status`	No	open (default) \| closed \| all
`category`	No	Comma-sep category ids (e.g. "wildfires,severeStorms")
`magnitude_id`	No	Filter by magnitude id (e.g. "ac" for acres)
`magnitude_max`	No	Maximum magnitude
`magnitude_min`	No	Minimum magnitude

Output Schema

TableJSON Schema

Name	Required	Description
`link`	No
`title`	No
`events`	No	List of natural events
`description`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedJul 29, 2026
- addedOutput schema / properties / description
```
Added value: +{
+  "type": "string"
+}
```
- changedOutput schema / properties / events / items / properties / closed / type
```
Previous value: -[
-  "string",
-  "null"
-]New value: +"null"
```
- changedOutput schema / properties / events / items / properties / description / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- addedOutput schema / properties / events / items / properties / geometry / items / properties / coordinates / items
```
Added value: +{
+  "type": "number"
+}
```
- addedOutput schema / properties / events / items / properties / geometry / items / properties / magnitudeUnit
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / events / items / properties / geometry / items / properties / magnitudeValue
```
Added value: +{
+  "type": "number"
+}
```
- addedOutput schema / properties / link
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / title
```
Added value: +{
+  "type": "string"
+}
```
- removedOutput schema / required
```
Removed value: -[
-  "events"
-]
```

Changed2 schema fields changedMay 24, 2026

addedInput schema / examples

Added value: +[
+  {
+    "days": 30,
+    "limit": 50,
+    "status": "open"
+  },
+  {
+    "bbox": "-120,40,-110,35",
+    "category": "wildfires,severeStorms",
+    "days": 60,
+    "status": "all"
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "events": {
+      "description": "List of natural events",
+      "items": {
+        "properties": {
+          "categories": {
+            "description": "Event categories",
+            "items": {
+              "properties": {
+                "id": {
+                  "description": "Category id",
+                  "type": "string"
+                },
+                "title": {
+                  "description": "Category title",
+                  "type": "string"
+                }
+              },
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "closed": {
+            "description": "Closed date or null if open",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "description": {
+            "description": "Event description",
+            "type": "string"
+          },
+          "geometry": {
+            "description": "Geographic coordinates",
+            "items": {
+              "properties": {
+                "coordinates": {
+                  "description": "GeoJSON coordinates",
+                  "type": "array"
+                },
+                "date": {
+                  "description": "Observation date",
+                  "type": "string"
+                },
+                "type": {
+                  "description": "Geometry type (Point, Polygon)",
+                  "type": "string"
+                }
+              },
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "id": {
+            "description": "EONET event id",
+            "type": "string"
+          },
+          "link": {
+            "description": "Event link",
+            "type": "string"
+          },
+          "sources": {
+            "description": "Event sources",
+            "items": {
+              "properties": {
+                "id": {
+                  "description": "Source id",
+                  "type": "string"
+                },
+                "url": {
+                  "description": "Source URL",
+                  "type": "string"
+                }
+              },
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "title": {
+            "description": "Event title",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "events"
+  ],
+  "type": "object"
+}

First observedMay 13, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive behavior. The description adds context about the specific return fields (event id, title, category, dated geometry, links) and the filtering dimensions, enhancing transparency beyond the annotations without contradicting them.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact at two sentences, first identifying the data source and categories, second covering filters, returns, and intended use. It is efficient but the second sentence is dense and could be split for easier scanning.

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?

Given the rich output schema and annotations, the description fully orients the user by naming the data source, categories, filter types, return fields, and the question it answers. No critical 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?

The input schema covers all 9 parameters with descriptions, so the baseline is 3. The description merely re-lists filter types (status, days, category, bbox, source, magnitude) without adding new meaning, as the schema already provides details like the non-standard bbox order.

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 identifies the resource (NASA EONET natural hazard events), the action (filter and retrieve events), and the output (event id, title, category, geometry, links). It distinguishes from siblings like get_event by emphasizing the filtering and listing capability.

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?

Provides a clear use case: find active or recent natural hazard events by various filters. It does not explicitly name alternative tools or exclusions, but the context is unambiguous enough to know when to use this tool.

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

All Nasa Eonet tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.