ph-civic-data-mcp

Overview Schema Source Related Servers Discussions Admin

Latest PHIVOLCS earthquakes

get_latest_earthquakes

Read-onlyIdempotent

Fetch the latest earthquake events from PHIVOLCS, with optional filtering by minimum magnitude, location coordinates, and radius. Returns event details including distance when location filters are used.

Instructions

Get the latest earthquake events from PHIVOLCS.

Reads the live PHIVOLCS earthquake list, the same table shown at earthquake.phivolcs.dost.gov.ph. Give center_lat, center_lon, and radius_km together to filter events near one place, and each matched event then carries a distance_km field. Give all three together, or leave out all three. Examples:

get_latest_earthquakes() latest events, default filters get_latest_earthquakes(min_magnitude=4.0, limit=10) strong events only get_latest_earthquakes(center_lat=14.5995, center_lon=120.9842, radius_km=50) near Manila

On failure: an invalid trio, an out-of-range radius_km, center_lat, or center_lon gives validation_error true and data_status "invalid_request". An unreachable or unparsable PHIVOLCS list gives upstream_error true and data_status "unavailable". Both return results: [] with the real error in caveats.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Max events to return (default 20, max 100).
`region`	No	Filter by PH region/province/city name (partial match).
`radius_km`	No	Keep only events within this distance of (center_lat, center_lon). Give all three of center_lat, center_lon, and radius_km together, or none of them. Each returned event then carries a distance_km field.
`center_lat`	No	Latitude of a search point. Give with center_lon and radius_km to filter to events near one place instead of the full recent-events list.
`center_lon`	No	Longitude of a search point. Give with center_lat and radius_km.
`min_magnitude`	No	Minimum magnitude to include (default 1.0).

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv0.8.0Sep 7, 2026

addedInput schema / properties / center_lat

Added value: +{
+  "anyOf": [
+    {
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Latitude of a search point. Give with center_lon and\n        radius_km to filter to events near one place instead of\n        the full recent-events list."
+}

addedInput schema / properties / center_lon

Added value: +{
+  "anyOf": [
+    {
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Longitude of a search point. Give with center_lat and\n        radius_km."
+}

addedInput schema / properties / radius_km

Added value: +{
+  "anyOf": [
+    {
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Keep only events within this distance of\n       (center_lat, center_lon). Give all three of center_lat,\n       center_lon, and radius_km together, or none of them. Each\n       returned event then carries a distance_km field."
+}

Changed3 schema fields changedv0.5.0Jun 17, 2026

addedOutput schema / properties / result / anyOf

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

removedOutput schema / properties / result / items

Removed value: -{
-  "additionalProperties": true,
-  "type": "object"
-}

removedOutput schema / properties / result / type
```
Removed value: -"array"
```

Addedv0.4.0May 22, 2026
Removedv1.0.4Apr 20, 2026
Addedv1.0.2Apr 19, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Adds concrete behavioral details beyond the readOnly/idempotent annotations: describes empty results with caveats, validation_error flags, and upstream_error handling. This enriches the annotation-only view.

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?

Well-structured: purpose first, then grouped examples, then failure behavior. Each sentence adds value; no fluff or repetition.

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?

With an output schema present, not detailing return fields is acceptable. The description covers usage scenarios, parameter relationships, and error behavior, making it complete for the tool's complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Input schema covers all 6 parameters (100%), and the description adds the grouping constraint (center_lat, center_lon, radius_km must be given together or not at all) and explains the distance_km output field, exceeding the schema alone.

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?

States a specific verb and resource: 'Get the latest earthquake events from PHIVOLCS.' This clearly distinguishes it from siblings like get_usgs_earthquakes_ph and get_earthquake_bulletin.

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 with examples of default, filtered, and location-based calls, and describes failure modes. Does not explicitly contrast with similar earthquake tools, but the PHIVOLCS focus makes usage apparent.

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

Deploy Server