Skip to main content
Glama

science

by io.github.pipeworx-io
OverviewAdmin

Get Earthquakes

get_earthquakes
Read-onlyIdempotent

Retrieve up to 20 globally recent earthquakes from the USGS FDSN service, filtered by lookback period (1–30 days, default 1) and minimum magnitude (default 4.0). Returns magnitude, location name, depth (km), coordinates, time, and tsunami warning flag.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysNoLook back N days (1-30, default 1)
min_magnitudeNoMinimum magnitude (default 4.0)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countYesTotal number of earthquakes found
earthquakesYesList of earthquake events

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "description": "Total number of earthquakes found",
+      "type": "number"
+    },
+    "earthquakes": {
+      "description": "List of earthquake events",
+      "items": {
+        "properties": {
+          "depth_km": {
+            "description": "Depth in kilometers",
+            "type": "number"
+          },
+          "details_url": {
+            "description": "URL to USGS event details",
+            "type": "string"
+          },
+          "latitude": {
+            "description": "Event latitude",
+            "type": "number"
+          },
+          "location": {
+            "description": "Geographic location description",
+            "type": "string"
+          },
+          "longitude": {
+            "description": "Event longitude",
+            "type": "number"
+          },
+          "magnitude": {
+            "description": "Earthquake magnitude",
+            "type": "number"
+          },
+          "time": {
+            "description": "ISO 8601 timestamp of event",
+            "type": "string"
+          },
+          "tsunami_warning": {
+            "description": "Whether tsunami warning was issued",
+            "type": "boolean"
+          }
+        },
+        "required": [
+          "magnitude",
+          "location",
+          "time",
+          "latitude",
+          "longitude",
+          "depth_km",
+          "tsunami_warning",
+          "details_url"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "count",
+    "earthquakes"
+  ],
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "days": 7,
+    "min_magnitude": 5
+  },
+  {
+    "days": 1
+  }
+]
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, and non-destructive behavior. The description adds useful behavioral context: the external USGS FDSN service, the limit of 20 results, and the 1–30 day lookback constraint. No contradictions with annotations.

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?

Two sentences, front-loaded with the main action, and every clause contributes useful information (source, limits, filters, return fields). No redundant or filler content.

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?

The tool is simple (2 optional parameters) and has both annotations and an output schema. The description covers return fields and key constraints, making it self-sufficient for an agent to understand what it will get and how parameters affect results.

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% and both parameters have descriptions in the schema. The description essentially repeats the schema's parameter info (defaults and ranges) without adding new semantics, so it meets baseline but adds no extra value.

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 uses a specific verb ('Retrieve') with a clear resource ('globally recent earthquakes from the USGS FDSN service') and includes filtering criteria. It clearly distinguishes from sibling tools like get_air_quality and get_iss_location by specifying both the data type and source service.

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 clearly implies when to use this tool (when earthquake data is needed) and specifies the return fields, but it does not explicitly mention alternatives or exclusion cases. Context is sufficient for an agent to select it among siblings, though no direct contrast is provided.

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

All science 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