Skip to main content
Glama

Nasa Eonet

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Get Event

get_event
Read-onlyIdempotent

Fetch a single event by EONET id.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
event_idYesEONET event id (e.g. "EONET_6210")

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoEONET event id
linkNoEvent link
titleNoEvent title
closedNoClosed date or null if open
sourcesNoEvent sources
geometryNoGeographic coordinates
categoriesNoEvent categories
descriptionNoEvent description

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "event_id": "EONET_6210"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "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",
+            "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"
+}
  2. First observed

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, etc. Description adds no further behavioral traits beyond what annotations provide.

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?

Extremely concise (8 words), front-loaded with verb and resource, no wasted text.

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?

Complete for a simple fetch-by-id operation with full schema, comprehensive annotations, and an output schema (not shown but present).

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 coverage is 100%; description reinforces the parameter's purpose but adds no new 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?

Clearly states the action (Fetch), resource (single event), and identifier (EONET id). Distinguishes from sibling 'events' likely used for listing.

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 clear context to fetch a specific event, but lacks explicit exclusion criteria or mention of alternatives like 'events' for listing.

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

All Nasa Eonet toolsInspect
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.

Resources